Ansible roles: Separate installing postgres from configuring it
As a user, let me use the pulp3-postgres role in a way that only configures the postgres db without installing postgres (or SCL). This is helpful when I have either (a) vetted a postgres install process (eg a standardized role), or (b) an existing postgres server (or cluster) that the pulp db should be added to.
Currently, the postgres role unconditionally installs SCL and then uses a fork of geerlingguy.postgresql to install postgres.
It looks like an older version used a different role and had a flag that disabled running the installation tasks. A flag (defaulting to on) would satisfy me.
#2 Updated by firstname.lastname@example.org about 1 year ago
- Status changed from NEW to ASSIGNED
- Assignee set to email@example.com
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
- Sprint set to Sprint 49
- Tags Pulp 3 added
Thanks, yes-- this is a reasonable request and it needs to be done very soon, so I'm taking it.
#3 Updated by firstname.lastname@example.org about 1 year ago
- Status changed from ASSIGNED to POST
@cognifloyd, my use case for this work is somewhat complex and still relies on some other changes. If you have the chance, please try this out and let me know if it fixes your case.
#4 Updated by email@example.com about 1 year ago
- Status changed from POST to MODIFIED
Applied in changeset ansible-pulp3|e55b0f8380c5c99163dd79139cce22aaf5506d25.
Please register to edit this issue