feat: environment type configurations #1496
Merged
Conversation
This file contains 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
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.
Environment type configurations
This is quite a major change to the keelconfig.yaml. Previously, only environment variables were specifiable by environment type (
staging,production, etc.). This has now been entirely removed fromkeelconfig.yamland we have introduced thekeel.staging.yamlandkeel.production.yamlconfig files as a means to set your hosted environments.If
keel.{ENVTYPE}.yamldoes not exist, then the defaultkeelconfig.yamlwill be used. Note that there is no inheritance of individual values between configs.