Ops to configure external blobstore to use AWS S3 Compatible Object Storage #1118
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?
Ops to configure external blobstore to use AWS S3 Compatible Object Storage (e.g. Min.IO)
Has a cf-deployment including this change passed cf-acceptance-tests?
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?
Ops to configure external blobstore to use AWS S3 Compatible Object Storage (e.g. Min.IO)
Does this PR introduce a new BOSH release into the base cf-deployment.yml manifest or any ops-files?
What is the level of urgency for publishing this change?
Tag your pair, your PM, and/or team!
kinjelom