From 8d30f19c8c1e67bbbf388aac8f4d9fd3eee56ee5 Mon Sep 17 00:00:00 2001 From: admin Date: Thu, 30 Jul 2026 22:03:44 -0700 Subject: [PATCH] postgresql.yaml: update stale comment referencing old CLONE_* rationale to reference standby_cluster design (no functional change - this file never used CLONE_* itself) --- postgresql/postgresql.yaml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/postgresql/postgresql.yaml b/postgresql/postgresql.yaml index b9fdb35..540952b 100644 --- a/postgresql/postgresql.yaml +++ b/postgresql/postgresql.yaml @@ -161,9 +161,11 @@ services: SPILO_CONFIGURATION: | bootstrap: post_init: /scripts/post_init_wrapper.sh "zalandos" - # CLONE_* vars intentionally omitted here — enabled only at cutover - # (Phase 3) to seed from the existing 41GB single instance via - # pg_basebackup. See ADR-0001 note before cutover. + # standby_cluster is NOT configured in this steady-state bootstrap file — + # it only applies during Phase 3 cutover staging + # (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: - postgresql_password - postgresql_replication_password