While reviewing #640 (log levels for Foreman & Proxy), @evgeni noted that adding a new environment variable to Foreman containers requires editing multiple podman_container tasks in the same file. The same duplication exists for Podman secrets.
Proposed solution
Follow the pattern already used in the pulp role (src/roles/pulp/defaults/main.yaml).
Define reusable variable maps in src/roles/foreman/defaults/main.yaml (or a dedicated vars file), e.g.:
foreman_container_base_env — env vars common to most/all Foreman containersforeman_container_base_secrets — secrets common to most/all Foreman containers
While reviewing #640 (log levels for Foreman & Proxy), @evgeni noted that adding a new environment variable to Foreman containers requires editing multiple podman_container tasks in the same file. The same duplication exists for Podman secrets.
Proposed solution
Follow the pattern already used in the pulp role (
src/roles/pulp/defaults/main.yaml).Define reusable variable maps in src/roles/foreman/defaults/main.yaml (or a dedicated vars file), e.g.:
foreman_container_base_env— env vars common to most/all Foreman containersforeman_container_base_secrets— secrets common to most/all Foreman containers