I have created a service that I use in a blueprint. This service takes input from an artifacts. The artifacts we use (scripts) are simple kept on an NFS share.
However I struggle to get a few things working:
1- In the Artifact Repository, there is a section Artifact Identifier Properties. How should that be used? There is always an entry there ARTIFACT_NAME. How can I use that?
2- It looks like the values given to properties (e.g.. the Repository Access Properties) are not always propagated through the deployment phase, resulting in an empty but required parameter issue?
Hope somebody can shed some light on this, as the documentation does not include any such info unfortunately, and Google is not giving much either.
PS This is in vCloud Automation Center v6.1.0.
I have now seen the Yum and Jenkins artifact repository specs and this confirms that things are not working as they should.
For example, the ARTIFACT_NAME does not get populated, so the RESOLVE artifact script doesn't know what to resolve.
Some of the properties from the repository spec also don't get propagated during deployment, resulting in empty values or variables showing old/obsolete values.
Other than that... I have it "working".