Be more explicit with Nordix CICD ONAP stack name 24/2024/3
authorFatih Degirmenci <fdegir@gmail.com>
Fri, 23 Aug 2019 07:49:43 +0000 (07:49 +0000)
committerFatih Degirmenci <fdegir@gmail.com>
Fri, 23 Aug 2019 08:08:52 +0000 (08:08 +0000)
commit9c661b6edf9d33fb07d998bf2440c0e92a43109e
tree391d951ed902a406d60ac17635fa47db015a2910
parent4e95f941f27d2907d983620ed992e8789e4eb59b
Be more explicit with Nordix CICD ONAP stack name

We need to differentiate between user initiated deployments
and CICD ones so we know who created a certain stack.

For CICD deployments, stack name will be in following form
  nordix-cicd-onap-{onap-branch}-{onap-flavor}
such as
  nordix-cicd-onap-master-full
  nordix-cicd-onap-dublin-core

For user initiated deployments, stack name will be set to
something random in following form in engine
  nordix-custom-onap-{random-string}
such as
  nordix-custom-onap-aglee

Change-Id: I145d8a6f4e3d624ef723f8decfbab0ce5297f45a
jjb/cloud-infra/cloud-infra-periodic-onap.yaml
jjb/cloud-infra/delete-heat-stack.sh
jjb/cloud-infra/onap-macros.yaml