fix(supabase): e2e:avatar runs on the sandbox only, DEV runner removed
scripts/avatar-e2e.sh read the DEV keys through `supabase status`, started the worker on the DEV network and let the suite write and purge on DEV. Port the V1-2 sandbox runner (`db-sandbox.sh avatar-e2e`: loopback gateway, worker in a 600 env file) and the guarded suite (fixed URL, container and key issuer, per-run accounts); refusals and the positive run proven under strace in .claude/audits/2026-11-02-avatar-e2e-sandbox-only.md.
This commit is contained in:
1 parent
6287e5bb9f
commit
3a4614bc86
17 files changed
+589
-117
No files matched your search
@@ -111,8 +111,8 @@ pinned toolchain from `rust-toolchain.toml` on first use; see
|
||||
`docs/development/RUST.md` §1 for the three `cargo install` / `rustup
|
||||
target add` lines and the Docker alternative. The files worker (profile
|
||||
photos, Step 8) runs as a container beside the local Supabase stack:
|
||||
`pnpm worker:image`, then `pnpm e2e:avatar` for the real-stack end-to-end
|
||||
run, or `docker compose --profile worker up worker` with a `.env.worker`
|
||||
`pnpm worker:image`, then `pnpm e2e:avatar` (= `pnpm db:sandbox avatar-e2e`) for the
|
||||
real-stack end-to-end run on the throwaway stack, or `docker compose --profile worker up worker` with a `.env.worker`
|
||||
(`docs/development/STORAGE.md`).
|
||||
|
||||
Docker Compose (matches production topology):
|
||||
|
||||
Reference in new issue
Block a user