feat: Adds ability to supply your own clouds.yaml config secret#24
Open
nicholaskuechler wants to merge 1 commit intoopenstack-exporter:masterfrom
Open
feat: Adds ability to supply your own clouds.yaml config secret#24nicholaskuechler wants to merge 1 commit intoopenstack-exporter:masterfrom
nicholaskuechler wants to merge 1 commit intoopenstack-exporter:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We're using ExternalSecrets operator and would like to use the secret created by that instead of hard-coding the clouds.yaml in the values.yaml.
This change preserves the current default behavior, but if you supply the name of your custom secret in values.yaml such as:
Then this custom secret will be used instead of the value of
clouds_yaml_config.