fix(#577): Support for layering configuration #578
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
In complex build pipelines it's not easy to set up all evitaDB parameters in one shot. It would be helpful if we could layer the `evita-configuration.yml` so that we first load the full configuration with defaults and then apply shorter versions that override only part of those settings. The overriding configurations could be expected to be in the same folder as the default configuration and could be applied in alphabetical order - i.e: 1. evita-configuration.yml 2. evita-configuration-environment.yml 3. evita-configuration-project.yml
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.
In complex build pipelines it's not easy to set up all evitaDB parameters in one shot. It would be helpful if we could layer the
evita-configuration.ymlso that we first load the full configuration with defaults and then apply shorter versions that override only part of those settings. The overriding configurations could be expected to be in the same folder as the default configuration and could be applied in alphabetical order - i.e: