Nested suborg settings

[martinm82]

I am trying to make use of safe-settings in our corporation but struggling a bit with avoiding duplication in the repo and suborg setting files. For that purpose I was thinking to either generate the safe-settings configuration based on some template files (e.g. jinja2) or by completely reorganising the way how safe-settings manages the setting files.

In a corporation you have usually more suborgs (multiple departments with units each with their own teams, etc.). Currently one can only have a suborg for a set of repositories.

The example below should make it more clear what I would like to have in safe-settings:

org/
  - main.yml                 <-- Global org settings
  - subOrgA/
    - main.yml               <-- Common subOrgA settings
    - subOrgAA/
      - main.yml             <-- Custom subOrgAA settings + inherited settings from subOrgA
      - repoAAA/
        - main.yml           <-- Custom repo settings + subOrgAA + subOrgA settings
      - repoAAB/
        - main.yml
      - repoAAC/
        - main.yml
   - subOrgB/
     - main.yml

This organization would as well simplify assigning CODEOWNERS per nested suborgs:

org/*                                    @acme-org/admins
org/subOrgA/*                    @acme-org/teamA
org/subOrgA/subOrgAA/* @acme-org/teamB 

I would like to get your input on this idea and whether it would cover as well other use cases.