controller_schedules.yml

In these files we configure the schedules for automation controller.
we will probably do this on each environment separately, as the hostnames differ.

group_vars/all/controller_schedules.yml

Here we see an empty set for all.

---
controller_schedules_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_schedules.yml

As we do not configure extra schedules in development, this file is an empty set.
(We use the containerized setup version, so no need for schedules).

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

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

group_vars/prod/controller_schedules.yml

As we do not configure extra schedules in prod, this file is an empty set.

---
controller_schedules_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: - controller_schedules_all
- controller_schedules_

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

Back