Minimize duplication between multiple environments

using role inheritance works well.

example - this is a role pv-aem-cms-all.yaml defined in the configuration-management project part:

it inherits two roles defines by an AEM applications which contain all osgi configs, application packages etc.
additional the role contains all configuration that is common for all environments.
within the environments only the role pv-aem-cms-all is references, inhering all files and all common configuration from this role.

the YAML extension magnolia uses are somewhat "proprietary", and they seem to have implemented their own yaml parser and extensions for it
https://documentation.magnolia-cms.com/display/DOCS56/YAML+inherit+and+include

i'm not sure if we should go this way and extend our YAML processing like this.

a better approach i my opinion is:

• create custom CONGA roles for your project hat inherit from the generic roles of AEM definitions (e.g. aem-cms, aem-dispatcher)

• define all configuration that is project-specific but common for all stages/environments in the custom role

• include these custom roles in the environments - now you should have not duplication in the environment because all shared config resided in the role definition

the role inheritance feature was introduced in CONGA 1.4.0 ().

For reference, here is the documentation of how Magnolia is handling the problem within their YAML definitions:
https://documentation.magnolia-cms.com/display/DOCS56/Reusing+configuration

the YAML file format does not have any support for include/import statements, see also https://stackoverflow.com/q/528281

some YAML libaries add support for a syntax like !include xyz.yaml - but this is a proprietary extension. other products express custom import statements as part of their YAML grammar. not sure which way we should take

can you share some use cases you see for this? do we need it only for the "global" section in the environment files, or for other places as well?