Support arbitrary cloud-config by default #88
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously example test manifests hardcoded defaults suitable for a bosh-deployment based environment. Internally we have other environment types that use different conventions.
This change adjusts ./scripts/deploy to more easily allow overriding these conventions by setting environment variables. The defaults remain aligned with the existing bosh-deployment conventions, but a caller can now set BOSH_VAR_{network,azs,vm_type} to override the relevant infrastructure setting.
The e2e-tests have also been updated to use the BOSH_VAR convention rather than the bespoke and less descriptive "PXC_TEST" prefix for discovering parameters from environment variables.
TNZ-70251