fix(cutover): remount honcho postgres init import #590

Merged

pdurlej merged 1 commit from codex/m01-remount-honcho-postgres-init into main

2026-05-29 00:47:17 +02:00

codex commented

2026-05-29 00:41:15 +02:00

Collaborator

Canary status: local validation passed; Forgejo canary may remain pending due runner queue.

Summary

Remounts the honcho-postgres init script from the M01 legacy-import runtime tree instead of the legacy /opt/vps-home-platform-infra repo root path.

This is a narrow M01 live-dependency migration step. It does not delete legacy data, mutate the database contents, or change the persistent Postgres volume.

Canary Context Pack

Product story

M01 needs active containers to stop depending on /opt/vps-home-platform-infra so RS2000 legacy paths can later be quarantined safely before deletion.

What changed

honcho-postgres now mounts init SQL from ${PLATFORM_RUNTIME_HONCHO_POSTGRES_INIT_FILE:-/opt/pdurlej-platform/runtime/legacy-import/config/honcho/postgres/init.sql}.
The runbook documents the new init script path and one-cycle rollback env override.

Why it changed

The live container currently has a bind mount to /opt/vps-home-platform-infra/config/honcho/postgres/init.sql. That is one of the remaining M01 legacy references.

Files touched

compose/apps/compose.yaml
modules/honcho-postgres/runbook.md

Relevant context

M01 RS2000 closeout plan
Cutover gate: remount active legacy bind mounts before any quarantine/delete

Runtime evidence

Pre-copy completed on RS2000 before this PR:

source: /opt/vps-home-platform-infra/config/honcho/postgres/init.sql
target: /opt/pdurlej-platform/runtime/legacy-import/config/honcho/postgres/init.sql
target mode: 644
target size: 39

Known constraints

This service is a Postgres container. Runtime apply must recreate only honcho-postgres with --no-deps, then check container health and pg_isready.

Explicit out-of-scope

No DB data migration
No deletion
No quarantine/tombstone
No broad compose refactor
No issue/comment writer changes

Requested decision

Merge after local validation and standard checks. If Forgejo checks remain queued, admin force-merge is acceptable under the current nondestructive M01 plan.

Merge blockers

Compose config invalid
Missing target init file on RS2000
PR not mergeable against main

Validation

git diff --check: passed
PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json: passed

Rollback

Set PLATFORM_RUNTIME_HONCHO_POSTGRES_INIT_FILE=/opt/vps-home-platform-infra/config/honcho/postgres/init.sql in runtime env for one rollback cycle and recreate only honcho-postgres.

Canary status: local validation passed; Forgejo canary may remain pending due runner queue. ## Summary Remounts the `honcho-postgres` init script from the M01 legacy-import runtime tree instead of the legacy `/opt/vps-home-platform-infra` repo root path. This is a narrow M01 live-dependency migration step. It does not delete legacy data, mutate the database contents, or change the persistent Postgres volume. ## Canary Context Pack ### Product story M01 needs active containers to stop depending on `/opt/vps-home-platform-infra` so RS2000 legacy paths can later be quarantined safely before deletion. ### What changed - `honcho-postgres` now mounts init SQL from `${PLATFORM_RUNTIME_HONCHO_POSTGRES_INIT_FILE:-/opt/pdurlej-platform/runtime/legacy-import/config/honcho/postgres/init.sql}`. - The runbook documents the new init script path and one-cycle rollback env override. ### Why it changed The live container currently has a bind mount to `/opt/vps-home-platform-infra/config/honcho/postgres/init.sql`. That is one of the remaining M01 legacy references. ### Files touched - `compose/apps/compose.yaml` - `modules/honcho-postgres/runbook.md` ### Relevant context - M01 RS2000 closeout plan - Cutover gate: remount active legacy bind mounts before any quarantine/delete ### Runtime evidence Pre-copy completed on RS2000 before this PR: - source: `/opt/vps-home-platform-infra/config/honcho/postgres/init.sql` - target: `/opt/pdurlej-platform/runtime/legacy-import/config/honcho/postgres/init.sql` - target mode: `644` - target size: `39` ### Known constraints This service is a Postgres container. Runtime apply must recreate only `honcho-postgres` with `--no-deps`, then check container health and `pg_isready`. ### Explicit out-of-scope - No DB data migration - No deletion - No quarantine/tombstone - No broad compose refactor - No issue/comment writer changes ### Requested decision Merge after local validation and standard checks. If Forgejo checks remain queued, admin force-merge is acceptable under the current nondestructive M01 plan. ### Merge blockers - Compose config invalid - Missing target init file on RS2000 - PR not mergeable against main ## Validation - `git diff --check`: passed - `PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json`: passed ## Rollback Set `PLATFORM_RUNTIME_HONCHO_POSTGRES_INIT_FILE=/opt/vps-home-platform-infra/config/honcho/postgres/init.sql` in runtime env for one rollback cycle and recreate only `honcho-postgres`.

codex added 1 commit

2026-05-29 00:41:15 +02:00

fix(cutover): remount honcho postgres init import

canary-required / collect-diff (pull_request) Successful in 4s

Details

patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s

Details

platformctl plan / auto-apply scope (pull_request) Successful in 22s

Details

base-is-main / guard (pull_request) Successful in 1s

Details

canary-required / canary (pull_request) Has been skipped