As a pulp_installer user, I can use the full logic to add repos to the system no matter which role I apply
As mentioned in #7773 , we should refactor our logic to add repos to the system (in a robust & configurable manner) into another role like
I propose the following design:
- This is a dependency role. pulp_common, pulp_redis, pulp_database, will all depend on it.
- When a role like pulp_common depends on it, it passes variables like
__pulp_repos_epel: trueto denote which repos the role needs. It passes variables via roles/pulp_common/meta/main.yml :
- If a user wants to disable the logic to add the repo (if they added it manually), they'll pass a variable like
pulp_repos_epel: falseto disable it.
- Existing variables for configuring how we add the repos to the system, like
epel_release_packages, should still used.
This logic is found in:
Please register to edit this issue