Remove PostgreSQL database after migrating to ext DB & other ext DB cleanups
After the DB is unmanaged and no longer needed, it should be removed to free up resources. It also removes a step where PostgreSQL is stopped and started again. Then it also does some preparations for non-Katello builds with the aim of later supporting this workflow on vanilla Foreman.
- [ ] I am familiar with the contributing guidelines.
Please cherry-pick my commits into:
- [ ] Foreman 3.8/Katello 4.10
- [ ] Foreman 3.7/Katello 4.9 (planned Satellite 6.14)
- [ ] Foreman 3.6/Katello 4.8
- [ ] Foreman 3.5/Katello 4.7 (Satellite 6.13)
- [ ] Foreman 3.4/Katello 4.6 (EL8 only)
- [ ] Foreman 3.3/Katello 4.5 on EL7 & EL8 (Satellite 6.12 on EL8 only; orcharhino 6.4/6.5 on EL8 only)
- [ ] Foreman 3.2/Katello 4.4 on EL7 & EL8
- [ ] Foreman 3.1/Katello 4.3 on EL7 & EL8 (Satellite 6.11 EL7/8; orcharhino 6.3 on EL7/8)
- We do not accept PRs for Foreman older than 3.1.
The PR preview for 3f4f94088aa89ee614830481331b7c591a6632ab is available at theforeman-foreman-documentation-preview-pr-2514.surge.sh
The following output files are affected by this PR:
Reviewed commit by commit > I could not add any suggestions on GitHub, but I'm pretty sure you understand what I mean.
This is indeed an annoying limitation of GH.
@evgeni mind checking the DB removal steps?
@evgeni mind checking the DB removal steps?
done
@ekohl Please rebase to master.
@Lennonka I don't think I'll have time to finish this up in the near future, so anyone is welcome to take it over.
@ekohl Is still PR still necessary with step 6+7 in https://docs.theforeman.org/nightly/Administering_Project/index-katello.html#migrating-to-external-databases_admin? If so, please rebase. If not, please close.
Nope, in https://github.com/theforeman/foreman-documentation/pull/3264 you rebased it and got it merged.