hosts: db0: Promote to primary
All data have been migrated from the PostgreSQL server in Kubernetes and the three applications that used it (Firefly-III, Authelia, and Home Assistant) have been updated to point to the new server. To avoid comingling the backups from the old server with those from the new server, we're reconfiguring WAL-G to push and pull from a new S3 prefix.
This commit is contained in:
@@ -46,6 +46,6 @@ wal_g_aws_secret_access_key: !vault |
|
|||||||
wal_g_pg_config:
|
wal_g_pg_config:
|
||||||
AWS_ACCESS_KEY_ID: '{{ wal_g_aws_access_key_id }}'
|
AWS_ACCESS_KEY_ID: '{{ wal_g_aws_access_key_id }}'
|
||||||
AWS_SECRET_ACCESS_KEY: '{{ wal_g_aws_secret_access_key }}'
|
AWS_SECRET_ACCESS_KEY: '{{ wal_g_aws_secret_access_key }}'
|
||||||
WALG_S3_PREFIX: s3://pgbackup/spilo/postgresql-default/wal/15
|
WALG_S3_PREFIX: s3://pgbackup/pyrocufflink/main/15
|
||||||
AWS_S3_FORCE_PATH_STYLE: true
|
AWS_S3_FORCE_PATH_STYLE: true
|
||||||
AWS_ENDPOINT: https://burp.pyrocufflink.blue:9000
|
AWS_ENDPOINT: https://burp.pyrocufflink.blue:9000
|
||||||
|
|||||||
@@ -1 +0,0 @@
|
|||||||
postgresql_standby: true
|
|
||||||
|
|||||||
Reference in New Issue
Block a user