eda_event_stream.yml

In these files we configure the event streams for eda controller.
we will probably do this on a per environment basis.

variables

The api understands the following structure:

{
    "name": "",
    "credential_name": "",
    "organization": "",
    "headers": "",
    "forward_events": "" 
}

Below you can see examples of how this is used.

group_vars/all/eda_event_stream.yml

Here we see an example of the configuration for an event stream.

---
eda_event_stream_all: []
# No config on global level
...

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

As we do not configure extra event_stream in development, this file is an empty set.

---
eda_event_stream_dev:

  - name: Example Event Stream
    credential_name: Example Credential
    organization: ORG_EDA

...

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

group_vars/prod/eda_event_stream.yml

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

---
eda_event_stream_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: - eda_event_stream_all
- eda_event_stream_

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

Back