Config files can be built within an API and overwritten in externalized config folders.
Many times, is is beneficial to combine, rather than overwrite, these config files.
Ex.: statuses
APIs declare their own statuses.
Many organizations declare statuses as shared statuses for a given domain
Light framework declares its own statuses for the modules it is providing.
This feature should support the merge of config files, with the ability to fail the build/bypass duplicate values, in a configurable manner.
ddobrin
commented
5 years ago 
Config files can be built within an API and overwritten in externalized config folders. Many times, is is beneficial to combine, rather than overwrite, these config files.
Ex.: statuses APIs declare their own statuses. Many organizations declare statuses as shared statuses for a given domain Light framework declares its own statuses for the modules it is providing.
This feature should support the merge of config files, with the ability to fail the build/bypass duplicate values, in a configurable manner.