Experimental ops file for disabling CF CredHub #1179
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.
WHAT is this change about?
New experimental ops file
disable-cf-credhub.yml
to disable the co-deployed CredHub instances. Can be used together withdisable-interpolate-service-bindings.yml
.What customer problem is being addressed? Use customer persona to define the problem e.g. Alana is unable to...
Alana doesn't use CredHub-enabled service brokers and wants to save cost for her CF deployment.
Please provide any contextual information.
#1170
Has a cf-deployment including this change passed cf-acceptance-tests?
Ops files will be used for the "experimental" deployment. The CATs configuration will need a change to disable CredHub interpolation tests: https://github.com/cloudfoundry/relint-envs/pull/35
Does this PR introduce a breaking change? Please take a moment to read through the examples before answering the question.
How should this change be described in cf-deployment release notes?
New ops file
disable-cf-credhub.yml
is now available, in case you don't use CredHub-enabled service brokers.Does this PR introduce a new BOSH release into the base cf-deployment.yml manifest or any ops-files?
Does this PR make a change to an experimental or GA'd feature/component?
Please provide Acceptance Criteria for this change?
The jobs "experimental-deploy" and "experimental-cats" must succeed (I'd like to see "experimental-cats" fail first, however).
What is the level of urgency for publishing this change?