controller_organizations.yml

As the credentials for private automation hub are mapped in the base controller config, there is nothing to do here.

group_vars/all/controller_organizations.yml

Here we see an empty set for all.

---
aap_organizations_all: []
...

But you can already see that the variable name used here has the "_all" extension, so the variable will not be overridden as this is not quite a inventory.
Why we do this, will become clear in a moment.

group_vars/dev/controller_organizations.yml

No addition needed in development, this file is an empty set.

---
aap_organizations_dev: []
...

Here the variable has the "_dev" extension, so the variable will not be overridden.

group_vars/prod/controller_organizations.yml

No addition needed in production, this file is an empty set.

---
aap_organizations_prod: []
...

Here the variable has the "_prod" extension, so the variable will not be overridden.

When we run a pipeline for a certain environment, the inventory structure will provide us with 2 variables: - 'aap_organizations_all'
- 'aap_organizations_'

We will merge these 2 variables into 1: aap_organizations and feed this to the infra.aap_configuration.controller_organizations role.

Back