fix(cutover): authenticate Redis BGSAVE backups #311

Merged
pdurlej merged 1 commit from codex/f3/redis-backup-auth into main 2026-05-17 02:14:10 +02:00
Collaborator

Canary status: missing — Forgejo PR checks will run on open; operator merge after green/accepted evidence.

Canary Context Pack

Product story

Before the Honcho Redis/Postgres final-boss F3 smoke, backup-before-apply must actively prove Redis can checkpoint with auth instead of silently archiving whatever happens to be on disk.

What changed

  • Redis backup now runs redis-cli --no-auth-warning -a "$REDIS_PASSWORD" BGSAVE when REDIS_PASSWORD is available in the container.
  • The backup helper no longer swallows Redis BGSAVE errors except the safe background saving already in progress case.
  • Mount archiving still runs after the checkpoint request succeeds.

Why it changed

Honcho Redis requires authentication. The old helper ran unauthenticated redis-cli BGSAVE >/dev/null 2>&1 || true, which could hide NOAUTH and still proceed. That is too weak for F3 final-boss backups.

Files touched

  • scripts/cutover/backup-before-apply.sh

Runtime evidence

  • home-platform-honcho-redis-1 exposes a REDIS_PASSWORD env name and uses it in the container healthcheck.
  • home-platform-honcho-redis-1 is running/healthy.
  • home-platform-honcho-postgres-1 is running/healthy.
  • No unhealthy containers before this PR.

Known constraints

  • This does not parse Redis passwords from container command strings. If a Redis service lacks REDIS_PASSWORD env and requires auth, backup should fail closed instead of silently proceeding.
  • This PR does not run the F3 smoke; it prepares the backup helper for the next step.

Explicit out-of-scope

  • No compose changes.
  • No runtime mutation except later operator-run backup after merge.
  • No change to Postgres backup behavior.

Requested decision

Merge this before backing up honcho-redis.

Merge blockers

  • bash -n scripts/cutover/backup-before-apply.sh fails.
  • Redis backup command would leak secret values to logs.

Spec sources read

  • scripts/cutover/backup-before-apply.sh — backup helper being corrected
  • modules/honcho-redis/module.yaml — target final-boss module
  • modules/honcho-postgres/module.yaml — paired final-boss module
  • compose/apps/compose.yaml — Honcho Redis auth delivery pattern

Verification

  • bash -n scripts/cutover/backup-before-apply.sh -> OK
  • git diff --check -> OK

Closes: none

Canary status: missing — Forgejo PR checks will run on open; operator merge after green/accepted evidence. ## Canary Context Pack ### Product story Before the Honcho Redis/Postgres final-boss F3 smoke, `backup-before-apply` must actively prove Redis can checkpoint with auth instead of silently archiving whatever happens to be on disk. ### What changed - Redis backup now runs `redis-cli --no-auth-warning -a "$REDIS_PASSWORD" BGSAVE` when `REDIS_PASSWORD` is available in the container. - The backup helper no longer swallows Redis `BGSAVE` errors except the safe `background saving already in progress` case. - Mount archiving still runs after the checkpoint request succeeds. ### Why it changed Honcho Redis requires authentication. The old helper ran unauthenticated `redis-cli BGSAVE >/dev/null 2>&1 || true`, which could hide `NOAUTH` and still proceed. That is too weak for F3 final-boss backups. ### Files touched - `scripts/cutover/backup-before-apply.sh` ### Runtime evidence - `home-platform-honcho-redis-1` exposes a `REDIS_PASSWORD` env name and uses it in the container healthcheck. - `home-platform-honcho-redis-1` is `running/healthy`. - `home-platform-honcho-postgres-1` is `running/healthy`. - No unhealthy containers before this PR. ### Known constraints - This does not parse Redis passwords from container command strings. If a Redis service lacks `REDIS_PASSWORD` env and requires auth, backup should fail closed instead of silently proceeding. - This PR does not run the F3 smoke; it prepares the backup helper for the next step. ### Explicit out-of-scope - No compose changes. - No runtime mutation except later operator-run backup after merge. - No change to Postgres backup behavior. ### Requested decision Merge this before backing up `honcho-redis`. ### Merge blockers - `bash -n scripts/cutover/backup-before-apply.sh` fails. - Redis backup command would leak secret values to logs. ## Spec sources read - `scripts/cutover/backup-before-apply.sh` — backup helper being corrected - `modules/honcho-redis/module.yaml` — target final-boss module - `modules/honcho-postgres/module.yaml` — paired final-boss module - `compose/apps/compose.yaml` — Honcho Redis auth delivery pattern ## Verification - `bash -n scripts/cutover/backup-before-apply.sh` -> OK - `git diff --check` -> OK Closes: none
fix(cutover): authenticate Redis BGSAVE backups
Some checks failed
base-is-main / guard (pull_request) Successful in 1s
canary-required / collect-diff (pull_request) Failing after 4s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s
canary-required / canary (pull_request) Has been skipped
patchwarden-pr-sanity / sanity (pull_request) Successful in 20s
b918356fdb
Sign in to join this conversation.
No reviewers
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform!311
No description provided.