Best practices for organizing configuration artifacts for multiple tenants, modules and environments

[Fábio Uechi]

Hi, 

I'm working on a project where we need to manage configuration and deployment artifacts ( scripts, data, etc ) for multiple tenants, modules and environments ( QA, UAT, etc  ). We are currently organizing everything in one git repository using the following structure:

tenant1

     module1

        env1

        env2

     module2

        env1

        env1

tenant2

     module1

        env1

        env2

     module2

        env1

        env1

Has anyone faced a scenario like that? Does each Tenant and Module needs its own pipeline? Is it better to have the the artifacts in distinct git repositories?

thanks in advance

Fábio

[Bert Vanpeteghem]

Hi,

I have had a scenario where we had a multi tenant application. Each tenant had its own settings. Each environment also had its own settings.

We could build and deploy a package to a tenant/environment combination. The deploy made sure it combines the correct configuration into the package and was also aware of the environment (location, credentials, ...).

Configuration was more or less organized as:

tenant1

env1

env2

 tenant2

env1

env2

All was in one single (svn at the time) repository.