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.
Problem
Then initializing a new project the production.yaml file is created that will hold the deployment-specific configuration. At present, the entire base.yaml contents are reflected in production.yaml. This makes it difficult to spot the deployment-specific configuration.
Solution
This PR will filter base.yaml to only contain the
_install:
fields and the deployment specific fieldsatomicInstall
,kubeContext
,server_name
andmaintainer_email
. It will look like this: