Use public Garage endpoint for tofu state (CI jobs are containers) #11

Merged

founder merged 1 commit from codex/tofu-garage-endpoint into main

2026-07-26 03:01:35 +00:00

founder commented

2026-07-26 03:01:31 +00:00

Owner

CI failed: 127.0.0.1:3900 is the container, not the host, and Garage binds host-loopback only. Use https://blob.key.store (verified S3 API). 🤖 Generated with Claude Code

CI failed: 127.0.0.1:3900 is the container, not the host, and Garage binds host-loopback only. Use https://blob.key.store (verified S3 API). 🤖 Generated with [Claude Code](https://claude.com/claude-code)

founder added 1 commit

2026-07-26 03:01:31 +00:00

tofu: use public Garage endpoint for state (jobs run in containers)

Release: If Needed / Check (Release Needed) (push) Successful in 6s

Details

Infra: Cloud OpenTofu / Infra (Cloud OpenTofu) (push) Successful in 42s

Details

Release: Signing Preflight / Release (Signing Preflight) (push) Successful in 1m5s

Details

Deploy: API / Deploy (API) (push) Has been cancelled

Details

Deploy: Web / Deploy (Web) (push) Has been cancelled

Details

84a544d8d8

The first CI run against the Garage backend failed with
'dial tcp 127.0.0.1:3900: connect: connection refused'. cloud-tofu jobs run
in containers, so 127.0.0.1 is the container rather than the forge host, and
Garage binds only to the host loopback (127.0.0.1:3900) -- so the podman
gateway (10.88.0.1) is not reachable either. My earlier verification ran
directly on the host, where the loopback does work, which is why this only
surfaced in CI.

Use https://blob.key.store, which serves the Garage S3 API (verified: returns
Garage's S3 AccessDenied XML, not the website handler). Traffic is TLS and the
bucket is private, authenticated by the Garage credentials.

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