- Use the same role for staging and production db servers
- Update postgresql repository signing key
Related to T2736
Details
Details
- Reviewers
ardumont - Group Reviewers
System administrators - Maniphest Tasks
- T2736: Configure db1 as new staging db server
- Commits
- rSPSITE8590a5dc4379: refactor the postgresql declaration to configure the main cluster instance
rSPSITE1edb2d3d5da2: Update postgresql repository signing key
rSPSITEe77721c27515: Include db1 as a db server for staging
rSPSITEe0480b9ce36f: Use the same role for staging and production db servers
bin/octocatalog-diff
Diff Detail
Diff Detail
- Repository
- rSPSITE puppet-swh-site
- Branch
- T2736
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 16686 Build 25730: arc lint + arc unit
Event Timeline
| site-modules/role/manifests/swh_database.pp | ||
|---|---|---|
| 3 | I was gonna say something about it but fine in the end. We probably exchanged fast on it and forgot ¯\_(ツ)_/¯ ;) | |
| data/deployments/staging/common.yaml | ||
|---|---|---|
| 144 | @vsellier, we have to use the following for our incremental step experiment with db0 to work. pgbouncer::auth_hba_file: "/etc/postgresql/%{alias('swh::postgresql::cluster_name')}"/pg_hba.conf"(or override that value completely in db0.internal.staging.swh.network.yaml below) db0: $ grep pg_hba /etc/pgbouncer/pgbouncer.ini auth_hba_file = /etc/postgresql/11/main/pg_hba.conf -> cluster_name in there is 11/main not 12/main as we will start using for db1 | |
| data/deployments/staging/common.yaml | ||
|---|---|---|
| 144 | well, lookup instead of alias... | |
| data/deployments/staging/common.yaml | ||
|---|---|---|
| 144 | yes true, it's updated | |