-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
Jakarta Release
-
None
When a vnf template invokes the capability name generator function to create the vnf_name, an improperly formatted JSON message is sent, and the name generator function fails to create a valid name for the vnf_name. This issue was not present in Istanbul but has arisen in Jakarta. Attached are logs.Log of Failure to name generate in JSON blob.txt
// code p "capability-data": [ { "capability-name": "generate-name", "key-mapping": [ { "output-key-mapping": [ { "resource-name": "vnf_name", "resource-value": "${vnf_name}" } ], "payload": [ { "param-name": "resource-name", "param-value": "vnf_name" }, { "param-name": "resource-value", "param-value": "${vnf_name}" }, { "param-name": "external-key", "param-value": "${vnf-id}_vnf_name" }, { "param-name": "policy-instance-name", "param-value": "${vf-naming-policy}" }, { "param-name": "naming-type", "param-value": "VNF" }, { "param-name": "AIC_CLOUD_REGION", "param-value": "${aic-cloud-region}" } ] } ] } laceholder
