CLOUDP-87735: global secret configuration #222
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.
This PR allows the user to override the global API key Secret by passing the
global-api-secret-name
argument to the container. If the flag not provided - the name defaults to the<deployment_name>-api-key
As this cannot be tested by integration tests I've tested this manually: changed the deployment spec to the following:
and ensured, that the new Secret was used by the Operator instead of the default one