Build Tools for VMware Aria provides development and release management tools for implementing automation solutions based on the VMware Aria Suite and VMware Cloud Director. The solution enables Virtual Infrastructure Administrators and Automation Developers to use standard DevOps practices for managing and deploying content.
Other
48
stars
24
forks
source link
Unable to configure vrang.bp.unrelease.versions / UNRELEASE_BLUEPRINT_VERSIONS in config / installer #364
When trying to prevent cloud templates from being "unreleased", we can affect the release locally using vrang.bp.unrelease.versions but this cannot be set when doing package releases. As a result, when a release is performed all previous versions of a template are "unreleased".
Why is this important to us... it's because the VRA Terraform provider attempts to query the specific cloud template version and if it's missing, results in config drift that is inescapable. We need to retain all cloud template versions and they need to be published.
Steps to Reproduce
Make a change to a cloud template
Run some code to package and release... something like:
... where props_file is the path to the properties file that will be used to influence the deployment. This is where we would expect to be able to set UNRELEASE_BLUEPRINT_VERSIONS.
Preconditions: [What are the preconditions to reproduce the issue]
You have an existing cloud template with at least one version published
build tools unreleases all versions except the latest when doing a prepare/release.
Reproduces how often: [What percentage of the time does it reproduce]
100%
Component/s: [What are the Build Tools for VMware Aria components affected by the issue (e.g. "common/artifact-manager", "maven/plugins/vra-ng", "typescript/vrotest", etc)]
Affects Build/s: [Which are the Build Tools for VMware Aria releases / builds affected by the issue]
2.34+
Description
When trying to prevent cloud templates from being "unreleased", we can affect the release locally using vrang.bp.unrelease.versions but this cannot be set when doing package releases. As a result, when a release is performed all previous versions of a template are "unreleased". Why is this important to us... it's because the VRA Terraform provider attempts to query the specific cloud template version and if it's missing, results in config drift that is inescapable. We need to retain all cloud template versions and they need to be published.
Steps to Reproduce
... where props_file is the path to the properties file that will be used to influence the deployment. This is where we would expect to be able to set
UNRELEASE_BLUEPRINT_VERSIONS
.Preconditions: [What are the preconditions to reproduce the issue]
Expected behavior: [What you expect to happen]
Actual behavior: [What actually happens]
Reproduces how often: [What percentage of the time does it reproduce] 100%
Component/s: [What are the Build Tools for VMware Aria components affected by the issue (e.g. "common/artifact-manager", "maven/plugins/vra-ng", "typescript/vrotest", etc)]
Affects Build/s: [Which are the Build Tools for VMware Aria releases / builds affected by the issue] 2.34+
Environment
Client
Server
Failure Logs
Related issues and PRs
https://github.com/vmware/build-tools-for-vmware-aria/issues/104
Additional Context