From b2211e406e73b342fc192eeb7a2356d25e0badf3 Mon Sep 17 00:00:00 2001 From: Chris Alfano Date: Tue, 19 May 2026 09:25:50 -0400 Subject: [PATCH] feat(deploy): default CFP_DATA_BRANCH to published MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The data repo now carries a dedicated `published` branch (built from `empty` + merged `legacy-import`) that's the long-term runtime branch. `fixture` reverts to its original role — a small handful of curated test records for local development. Unblocked by #66 (PR #68): the entrypoint + Node reconciler now use an explicit fetch refspec, so switching `CFP_DATA_BRANCH` between branches no longer trips the single-branch-clone limitation that bit us earlier. The branch is overridable per-pod via the existing `CFP_DATA_BRANCH` env var — overlays can point a debug deployment at `fixture` or `legacy-import` without touching the base. Co-Authored-By: Claude Opus 4.7 (1M context) --- deploy/kustomize/base/configmap.yaml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/deploy/kustomize/base/configmap.yaml b/deploy/kustomize/base/configmap.yaml index 5ebdac9..0f95ff7 100644 --- a/deploy/kustomize/base/configmap.yaml +++ b/deploy/kustomize/base/configmap.yaml @@ -16,7 +16,13 @@ data: NODE_OPTIONS: "--max-old-space-size=1536" PORT: "3001" STORAGE_BACKEND: "filesystem" - CFP_DATA_BRANCH: "fixture" + # The runtime-served branch. `published` is the long-term sandbox + prod + # default — it accumulates importer snapshots (via merges from + # `legacy-import`) on top of new-in-v1 records the running API writes. + # Override per-pod via the `CFP_DATA_BRANCH` env var, e.g. point a debug + # deployment at `fixture` (small handful of seed records) or directly at + # `legacy-import` (raw snapshot, no merged runtime writes). + CFP_DATA_BRANCH: "published" # SSH key for the data repo deploy key (private branch reads). # accept-new keeps first-connect simple; strict host-key checking via # known_hosts ConfigMap is an overlay concern.