Skip to content

feat(deploy): default CFP_DATA_BRANCH to published #69

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
themightychris merged 1 commit into from
May 19, 2026
Merged

feat(deploy): default CFP_DATA_BRANCH to published #69

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion deploy/kustomize/base/configmap.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down