gateway_role_user_assignments

In this file we configure the role a user has within automation platform.

group_vars/all/gateway_role_user_assignments.yml

---
gateway_role_user_assignments_all:

  - role_definition: Organization Member
    user: wilco
    object_ids: MGT

  - role_definition: Organization Member
    user: coll_upload
    object_ids: MGT

  - role_definition: Team Member
    user: coll_upload
    object_ids: MGT
    team_name: hub_coll_team

  - role_definition: Organization Member
    user: coll_get
    object_ids: MGT

  - role_definition: Team Member
    user: coll_get
    object_ids: MGT
    team_name: hub_coll_team

  - role_definition: Organization Member
    user: ee_upload
    object_ids: MGT

  - role_definition: Team Member
    user: ee_upload
    object_ids: MGT
    team_name: hub_ee_team

  - role_definition: Organization Member
    user: ee_pull
    object_ids: MGT

  - role_definition: Team Member
    user: ee_pull
    object_ids: MGT
    team_name: hub_ee_team

  - role_definition: Organization Admin
    user: mgt
    object_ids: MGT

  - role_definition: Organization Admin
    user: CaC_admin_MGT
    object_ids: MGT
...

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_role_user_assignments.yml

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

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

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

group_vars/prod/gateway_role_user_assignments.yml

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

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

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

Back