postgresql.yaml: update stale comment referencing old CLONE_* rationale to reference standby_cluster design (no functional change - this file never used CLONE_* itself)
ci/woodpecker/push/deploy Pipeline was successful

This commit is contained in:
2026-07-30 22:03:44 -07:00
parent 4dcb3561ed
commit 8d30f19c8c
+5 -3
View File
@@ -161,9 +161,11 @@ services:
SPILO_CONFIGURATION: | SPILO_CONFIGURATION: |
bootstrap: bootstrap:
post_init: /scripts/post_init_wrapper.sh "zalandos" post_init: /scripts/post_init_wrapper.sh "zalandos"
# CLONE_* vars intentionally omitted here — enabled only at cutover # standby_cluster is NOT configured in this steady-state bootstrap file —
# (Phase 3) to seed from the existing 41GB single instance via # it only applies during Phase 3 cutover staging
# pg_basebackup. See ADR-0001 note before cutover. # (postgresql/cutover/postgresql-ha-staging.yaml), which streams
# continuously from the live single instance until promotion. See
# ADR-0001 Dry-Run Debugging Log note for the standby_cluster design.
secrets: secrets:
- postgresql_password - postgresql_password
- postgresql_replication_password - postgresql_replication_password