Actions
Refactor #7037
closed
Split the pulp_database role into 2 roles: database vs config
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 76
Quarter:
Description
Per https://pulp.plan.io/issues/7005#note-11
We should split pulp_database into 2 roles:
- pulp_database (that is basically the content of install_db playbook) - And that people might feel free to not call at all.
- pulp_database_configuration (that is the migration really taking place) - That is mandatory to be run.
Currently, whether or not to install the database is controlled by the var pulp_install_db.
Related issues
Actions
.
Split the pulp_database role into 2 roles:
pulp_database vs pulp_database_config
Includes removing the variable pulp_install_db.
Necessitates a new role list for those not using
pulp_all_servicesfixes: #7037 Split the pulp_database role into 2 roles: database vs config https://pulp.plan.io/issues/7037