allow configuration file named per component #31
Merged
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.
implements #28
If component configuration file contains
subcomponent_config_file:
key, disregarding the value of this key, configuration won't be merged to master config. Otherwise anything found within yaml file is merged both to master config, and to appropriate component config.One idea coming out of this implementation is having a
cfhighlander scconfigextract
command which will generate these files for every subcomponent referenced in the template.