From a35f7135bf90ee74023857e9f5af9632320f80a4 Mon Sep 17 00:00:00 2001 From: Claude Fable 5 Date: Sun, 12 Jul 2026 19:58:19 +0200 Subject: [PATCH] Point the monthly restore drill at Prod (go-live #87) The runner on ONE holds dorfteich-prod_backups; since go-live the drill that proves a backup restores should target the live instance, not Test. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01EwZ4jR4KFAPvpjWevfUGX1 --- .gitea/workflows/drill.yml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/.gitea/workflows/drill.yml b/.gitea/workflows/drill.yml index a9298a5..9278d43 100644 --- a/.gitea/workflows/drill.yml +++ b/.gitea/workflows/drill.yml @@ -1,8 +1,11 @@ # Monthly restore drill (ADR 0015, issue #87): restores the latest backup # set of the drilled stage into a scratch environment on the runner's Docker # daemon (the stage host), verifies it, and logs the outcome as a comment on -# the pinned "Restore drills" issue. Pre-go-live the drilled stage is Test; -# switch DRILL_SOURCE_VOLUME to the Prod backups volume at go-live (#89). +# the pinned "Restore drills" issue. Since go-live (2026-07-12, #89) the +# drilled stage is Prod; the runner on ONE holds the dorfteich-prod_backups +# volume. TAG stays `test` on purpose: it only selects the drill-harness +# images (backup + api) that perform and verify the restore, and a forward +# schema restores a Prod set fine — it is not a claim about the Prod release. name: Restore drill @@ -18,7 +21,7 @@ on: env: IMAGE_BASE: gitea.101010.cloud/stwaidele/dorfteich - DRILL_SOURCE_VOLUME: dorfteich-test_backups + DRILL_SOURCE_VOLUME: dorfteich-prod_backups DRILL_LOG_ISSUE: '98' jobs: