hub_ee_images

For ee_images in automation hub to load through this interface, you will have to provide the files to load the images from.
As git isn't made for binary manangement, these should be hosted elsewhere and as we want config as code to be a complete unit, we will not use this.
Feel free to use it anyway.
We will show you another way to get these images into automation hub.

group_vars/all/hub_ee_images.yml

As we do not configure ee_images this way, this file is an empty set.

---
hub_ee_images_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/hub_ee_images.yml

As we do not configure ee_images this way, this file is an empty set.

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

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

group_vars/prod/hub_ee_images.yml

As we do not configure ee_images this way in automation hub, this file is an empty set.

---
hub_ee_images_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: - hub_ee_images_all
- hub_ee_images_

We will merge these 2 variables into 1: hub_ee_images and feed this to the infra.aap_configuration.hub_ee_images 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:
        hub_ee_images: >
          {{ hub_ee_images_all |
          community.general.lists_mergeby(vars['hub_ee_images_' + branch_name],
          'name', recursive=true, list_merge='append') }}

This results in the hub_ee_images variable the collection needs.

Back