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?
We saw now in several situations that we are unable to solve issues fast, if we cannot access a failed or broken vm. We need access to the VM if the agent fails to startup so we can debug.
We want to have control over vcap password without interfering with other deployments.
Please provide contextual information.
https://www.starkandwayne.com/blog/how-to-lock-vcap-password-for-bosh-vms/index.html
What tests have you run against this PR?
How should this change be described in bosh release notes?
In case of fixed vcap-password in cloud-config the corresponding password is set during deployment of VM’s.
Does this PR introduce a breaking change?
No as long no one configure a vcap password in cloud-config.
Tag your pair, your PM, and/or team!
@ansh-SAP @anshrupani @a-hassanin @Sascha-Stoj @cf-bosh