fix(gateway): persist git-gate state across gateway restarts #513

Closed

didericis-claude wants to merge 1 commits from fix/gitgate-persist-512 into fix/firecracker-gateway-ca-persist-510

Author	SHA1	Message	Date
didericis	dff811f190	fix(gateway): persist git-gate state across gateway restarts tracker-policy-pr / check-pr (pull_request) Successful in 12s Details lint / lint (push) Successful in 59s Details test / unit (pull_request) Successful in 53s Details test / integration-docker (pull_request) Successful in 1m7s Details test / coverage (pull_request) Successful in 19s Details Per-bottle git-gate state (bare repos under /git/<id>, deploy creds under /git-gate/creds/<id>) was provisioned once at bottle launch and lived only in the gateway's ephemeral storage. A gateway rebuild/restart wiped it and nothing re-provisioned already-running bottles, so their agents 404'd on fetch/push. Same class of bug as the CA (#510); the orchestrator restores only egress tokens, not git-gate declarations. Persist the state on both backends, mirroring the CA-persistence approach: - firecracker: attach a second persistent data drive (/dev/vdc) to the gateway VM and bind-mount its git/ + creds/ subdirs onto /git and /git-gate/creds in the gateway guest init, before the data plane starts. Generalize the VM config to a stable-ordered data_drives tuple (CA=vdb, git=vdc; orchestrator registry stays vdb). - docker: bind-mount host dirs (host_gateway_git_dir / creds_dir, under the never-pruned app-data root) onto /git and /git-gate/creds, with BOT_BOTTLE_DOCKER_GIT_MOUNT / _CREDS_MOUNT env overrides so CI isolates them to per-run volumes it cleans up. Teardown already rm -rf's /git/<id> + creds, so the persistent store self-cleans over the normal lifecycle. Closes #512 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-26 17:34:22 -04:00

Author

SHA1

Message

Date

didericis

dff811f190

fix(gateway): persist git-gate state across gateway restarts

tracker-policy-pr / check-pr (pull_request) Successful in 12s

Details

lint / lint (push) Successful in 59s

Details

test / unit (pull_request) Successful in 53s

Details

test / integration-docker (pull_request) Successful in 1m7s

Details

test / coverage (pull_request) Successful in 19s

Details

Per-bottle git-gate state (bare repos under /git/<id>, deploy creds under
/git-gate/creds/<id>) was provisioned once at bottle launch and lived only
in the gateway's ephemeral storage. A gateway rebuild/restart wiped it and
nothing re-provisioned already-running bottles, so their agents 404'd on
fetch/push. Same class of bug as the CA (#510); the orchestrator restores
only egress tokens, not git-gate declarations.

Persist the state on both backends, mirroring the CA-persistence approach:

- firecracker: attach a second persistent data drive (/dev/vdc) to the
  gateway VM and bind-mount its git/ + creds/ subdirs onto /git and
  /git-gate/creds in the gateway guest init, before the data plane starts.
  Generalize the VM config to a stable-ordered data_drives tuple (CA=vdb,
  git=vdc; orchestrator registry stays vdb).
- docker: bind-mount host dirs (host_gateway_git_dir / creds_dir, under the
  never-pruned app-data root) onto /git and /git-gate/creds, with
  BOT_BOTTLE_DOCKER_GIT_MOUNT / _CREDS_MOUNT env overrides so CI isolates
  them to per-run volumes it cleans up.

Teardown already rm -rf's /git/<id> + creds, so the persistent store
self-cleans over the normal lifecycle.

Closes #512

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-26 17:34:22 -04:00

fix(gateway): persist git-gate state across gateway restarts #513

1 Commits