Global parameters - Stored in specific Factory JSON files - A bit confusing when moving development branch/repository between different ADF

Question

Using GIT as source control, the global parameters are stored on the development branch in the "factory" folder in a JSON file having the same name as the Factory. This way, If we have more than one ADF connected to the same GIT repository and the same branch, we can have different global parameter values (and parameters) define.
Note: When publishing, the global parameters are stored in the adf_publish branch.

So far so good.

Now to what's a bit confusing. When connecting another ADF to the same GIT repository, the Factory specific JSON file is not created and hence, no global parameters exists. One way to have the factory specific JSON file created for you is to define a global parameter, but I'm sure there's also other ways.

It would be much better if the Factory specific JSON file was automatically created at the time the Factory was connected to the GIT repository. I understand that when doing so, it's not clear with what global parameters this Factory JSON file shall be populated with since the factory folder already could contain more than one Factory, but a suggestion is that the user get's the option to choose from what Factory to copy the global parameters and if the values of the global parameters shall be populated of being left empty.

Adding a picture below where one can see three Factories and the global parameter definitions. The "tt" parameter I created just to enforce the creation of the factory JSON file.

One might argue that we only shall have one Factory connected to a specific GIT repository, but there are reasons not to follow that rule, while moving the development environment from one Factory to another Factory is one of the reasons

Answer 1

Hello and welcome to Microsoft Q&A @Pär Adeen .

It looks like you are doing a non-standard organization of Factories and Git. I would like to get a little more clarity on the goals here.
Usually there is one Factory for each environment (dev, test , prod). Here you are "... moving the development environment from one Factory to another Factory ...". So you want to have your development branch/environment straddling 2 Factories? Can you tell me why, or what this is in pursuit of?

During a "Publish" action, the collaboration branch is pushed to the Factory's "Live Mode" and "adf_publish" branch. This action keeps the Live Mode and adf_publish in synch. However if there are two Factories reading from the same Git, only one of them would receive the benefit of this synchronization. The one not involved in the Publish action will remain with outdated "Live Mode".