gateway_service_keys

We do not make use of this yet, we will probably configure this later.

group_vars/all/gateway_service_keys.yml

As we do not configure extra service keys in rhaap, this file is an empty set.

---
gateway_service_keys_all: []
  # No extra config exists
...

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/gateway_service_keys.yml

As we do not configure extra service keys in rhaap, this file is an empty set.

---
gateway_service_keys_dev: []
  # No extra config exists
...

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

group_vars/prod/gateway_service_keys.yml

As we do not configure extra service key in rhaap, this file is an empty set.

---
gateway_service_keys_prod: []
  # No extra config exists
...

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: - gateway_service_keys_all
- gateway_service_keys_

We will merge these 2 variables into 1: gateway_service_keys and feed this to the infra.aap_configuration.gateway_service_keys role.
In main.yml the merge of the variables is done by this piece of code:

    - name: Set the gateway vars
      ansible.builtin.set_fact:
        gateway_service_keys: >
          {{ gateway_service_keys_all |
          community.general.lists_mergeby(vars['gateway_service_keys_' + branch_name],
          'name', recursive=true, list_merge='append') }}

This results in the gateway_service_keys variable the collection needs.

Back