S3 config should not stomp local secret config#106
S3 config should not stomp local secret config#106openshift-merge-robot merged 2 commits intoopenshift:masterfrom coreydaley:github_99_s3_config_should_not_stomp_local_secret_config
Conversation
|
/retest |
|
/retest |
1 similar comment
|
/retest |
bparees
left a comment
There was a problem hiding this comment.
good start, the main thing you're missing is reacting to changed/deletion/creation of the user-defined secret.
|
@bparees ptal |
|
/retest |
|
@bparees ptal I am still working on the test, but I believe everything else is ready for another look. |
bparees
left a comment
There was a problem hiding this comment.
why is this PR disabling all our tests?
|
@bparees ptal |
|
/retest |
Checks for a user supplied S3 configuration to use
If user config is not found, use the system configuration
Add a test to ensure that a user provided configuration will override the sytem provided one
Add image-registry-private-configuration-user to the README.md
Finalize S3 storage (remove bucket if managed by us)
Don't fail on S3 bucket tagging and encryption, just set the appropriate conditions to false
Fixes #79
Fixes #99
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, coreydaley The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Cluster S3 configuration should not stomp user configuration
Fixes #79
Fixes #99