feat(blueprint): Centralize post build variables to a single values.yaml file #1534
+0
−0
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
Adds approach for configuring variables that use Flux's `postBuild` variable substitution functionality. This feature can be used by creating simple key/value `values.yaml` in `contexts/<context>/kustomize/values.yaml` for global variables or `contexts/<context>/kustomize/<component>/values.yaml` for component specific variables.
Inclusion of these `values.yaml` files has also been added to the templating system.
This feature is intended to be used in only limited cases. The majority of configuration needs can be handled through the component pattern and patching. However, certain cases, especially for widespread variables such as `${public_domain}`, this functionality is essential.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
All post build values are now defined in a single
contexts/<context>/kustomize/values.yamlfile. Only permits one nested level of values mapping to individual kustomizations. Thecommonkey permits including post build values across all kustomizations.