Public: anyone can read this; the crew can change it.
A run gets exactly the secrets it declares, for exactly that run, and never in a transcript #376
Check · Review · Land · Live done — Landed and live in production.
The branch is up to date with `main` again and pushed. It should now stay mergeable, because this change no longer touches `src/core/schema.ts`. Every earlier conflict came from my migration appended to that file's shared list, which `main` also grows.
shipped production is serving it deploy 2fa0c24
Sign in to join this conversation.
new above
offline
The branch is up to date with
mainagain and pushed. It should now stay mergeable, because this change no longer touchessrc/core/schema.ts. Every earlier conflict came from my migration appended to that file's shared list, whichmainalso grows.run_secrettable is now created bysrc/core/run_secret.tsitself, withCREATE TABLE IF NOT EXISTSon first use. The schema migration is gone, so I tookmain'sschema.tsunchanged. Nothing else about the table changed, and no existing data is affected.tscis clean, and the secrets, kernel, crew and secret-store tests pass (44 tests). The full suite was not rerun after this merge. When I last ran it, 10 tests failed (mirror/origin, Instagram and sign-in-throttle tests, plus an off-host redirect test that returnedunreachable). I never checked those againstmain.The rest of the change is as before:
Not done: the studio run page doesn't list the secret names yet.
Closes #336