diff options
author | 2018-08-23 11:49:12 -0400 | |
---|---|---|
committer | 2018-08-28 12:59:43 +0000 | |
commit | b1ce3d40b0f056a6275ab9ecb48fd0b16b9bb394 (patch) | |
tree | 6ba16bbaa02a24a8bc28612ab51c37d5f193066b /src/app/vnfs/build-artifacts/template-holder/template-configuration/template-configuration.component.ts | |
parent | 90018a9d2bb344fa103b123b5f9facc0d3738255 (diff) |
APPC CDT to Support Multiple Templates for VNFCs
APPC CDT Should Support Multiple Templates For Configure and
ConfigModify for VNFs with VNFC level templates.
CDT would be used to create a single reference artifact for a VNF.
For the Configure related actions (Configure and ConfigModify)
vnfc-type to be shown at the top. The user would have a new link
below it, to be able to add each vnfc-type. For each vnfc-type,
the user would create the associated template and PD file as usual.
The fix required to modify several visual elements and variables
related to VNFC Types on MyVNFS page, ReferenceData page, Template
page and Parameters page. Also a number of supporting services were
modified. New Modal window type is now used for VNFC-related dialogs.
Change-Id: Ibbbb50e2ff6f96783c0aea89a6870d7c28021ba0
Issue-ID: APPC-1010
Signed-off-by: od7427 <od7427@att.com>
Diffstat (limited to 'src/app/vnfs/build-artifacts/template-holder/template-configuration/template-configuration.component.ts')
-rw-r--r-- | src/app/vnfs/build-artifacts/template-holder/template-configuration/template-configuration.component.ts | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/src/app/vnfs/build-artifacts/template-holder/template-configuration/template-configuration.component.ts b/src/app/vnfs/build-artifacts/template-holder/template-configuration/template-configuration.component.ts index 6cae746..0be5f68 100644 --- a/src/app/vnfs/build-artifacts/template-holder/template-configuration/template-configuration.component.ts +++ b/src/app/vnfs/build-artifacts/template-holder/template-configuration/template-configuration.component.ts @@ -45,6 +45,7 @@ const PARAM_DATA:string="param_data"; const TEMPLATE_DATA:string="template_data"; @Component({ selector: 'app-golden-configuration', templateUrl: './template-configuration.component.html', styleUrls: ['./template-configuration.component.css'] }) export class GoldenConfigurationComponent implements OnInit { + clName= "TemplateConfigCompon"; @ViewChild('templateeditor') templateeditor; @Input() configMappingEditorContent: string; @Input() isMappingComp: boolean; @@ -154,7 +155,13 @@ export class GoldenConfigurationComponent implements OnInit { //======================================Start of ngOnInit() Method============================================ ngOnInit() { + var methName= "ngOnInit"; + if( this.utilityService.getTracelvl() > 0 ) + console.log( this.clName+": "+methName+": start."); var refObj = this.refObj = this.prepareFileName(); + if( this.utilityService.getTracelvl() > 0 ) + console.log( this.clName+": "+methName+ + ": refObj:["+JSON.stringify(refObj)+"]"); if (refObj && refObj != undefined) { this.item = refObj; @@ -162,6 +169,10 @@ export class GoldenConfigurationComponent implements OnInit { this.vnfcType = this.item.scope["vnfc-type"]; this.protocol = this.item['device-protocol']; this.action = this.item.action; + if( this.utilityService.getTracelvl() > 0 ) + console.log( this.clName+": "+methName+": vnfType:["+this.vnfType+ + "] vnfcType:["+this.vnfcType+"] protocol:["+this.protocol+"] action:["+ + this.action+"]"); this.artifactRequest.action = this.item.action; this.artifactRequest.vnfType = this.vnfType; if (this.vnfcType != undefined && this.vnfcType.length != 0) { |