Use postgresql_upgrade role from foreman-operations-collection for Fo…#1313
Conversation
aa2d97d to
c634930
Compare
ekohl
left a comment
There was a problem hiding this comment.
Also needs to upgrade instructions. Also update CI. I still really dislike adding a dependency on Ansible collections.
|
Here I have broken out to make the Pulp piece stand-alone: #1314 |
c634930 to
06a2f96
Compare
|
Job update -- theforeman/jenkins-jobs#18 |
06a2f96 to
e419a58
Compare
e419a58 to
b168aac
Compare
f7bf11c to
ab3b803
Compare
|
Left a few blocking comments, but overall this is the direction we should be aiming. I do wonder if the installation should default to |
ab3b803 to
bb759a7
Compare
Works for me to make it straight forward for the main use case. I updated the jenkins job PR as well. |
bb759a7 to
fdd29b1
Compare
|
@ekohl Looking for your final input here |
No, that's still my main issue. IMHO we should still strive to use less Ansible, not more. The risk I see is that we're building a foreman-maintain 2.0. However, I'm willing to step aside and let you deal with it. |
What I always find I am missing with these sort of comments is what the alternative is. If you are proposing we move away from Ansible, where should we head? |
|
I am wondering if the Foreman installer should take care of it. Personally I think we should also introduce an installer scenario that sets up just the PostgreSQL server for external DB access. Then you could reuse the code there. |
|
I think we discussed this (let installer do the pg10→12 upgrade) and ended up saying that this is a corner case (only needed upstream, only on el8, and at that time only Foreman) which we handle via docs/ansible. Looking at theforeman/foreman-installer#650, we wanted to pick it back to 2.4 -- to make Katello start out with 12 on el8, but never did. |
…reman upgrades