You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e70b775
Browse filesBrowse the repository at this point in the historyBrowse files
bench docs: name the script that refreshes the cache (#211)
vortex-data/vortex#11192 moved the cache revalidate out of
scripts/post-ingest.py into scripts/refresh-bench-site.py, which a
reusable workflow runs once per CI run. Update the contract, the
architecture docs, the secrets runbook, and two code comments to name
the new caller and describe when it runs and how it handles failure.
No behaviour changes.
Signed-off-by: Will Manning <will@willmanning.io>
Copy file name to clipboardExpand all lines: docs/bench/runbooks/deploy-secrets-setup.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -142,17 +142,17 @@ team's secret store. **Never paste a value into this document.**
142
142
| `BENCH_DB_POOL_MAX` | Max connections in the pg pool (default `8`; omit to use default) | Existing monorepo Vercel project env |
143
143
| `BENCH_DB_IDLE_TIMEOUT_MS` | Pool idle-connection timeout in ms (default `5000`; positive integer; omit to use default) | Existing monorepo Vercel project env |
144
144
| `BENCH_DB_CONNECTION_TIMEOUT_MS` | New-connection and pool-slot timeout in ms (default `5000`; positive integer; omit to use default) | Existing monorepo Vercel project env |
145
-
| `BENCH_REVALIDATE_TOKEN` | Bearer token for `POST /api/revalidate` — must match the value the monorepo's emitter caller (`post-ingest.py`) sends | Existing monorepo Vercel project env; coordinate with the monorepo caller (see note below) |
145
+
| `BENCH_REVALIDATE_TOKEN` | Bearer token for `POST /api/revalidate` — must match the value the monorepo's caller (`refresh-bench-site.py`) sends | Existing monorepo Vercel project env; coordinate with the monorepo caller (see note below) |
146
146
147
-
>**`BENCH_REVALIDATE_TOKEN` coordination:** this token authenticates the monorepo's `post-ingest.py`
147
+
>**`BENCH_REVALIDATE_TOKEN` coordination:** this token authenticates the monorepo's `refresh-bench-site.py`
148
148
> revalidation caller against `POST /api/revalidate`. Setting it on the new project only makes the new
149
149
> project ACCEPT a matching bearer — it does **not** redirect the emitter's traffic here. The emitter
150
150
> POSTs to whatever base URL it is configured with (currently the monorepo-owned project's domain), so
151
151
> until that target URL is repointed at this project (at the Phase-5 DNS cutover, or by updating the
152
152
> emitter's configured URL), revalidation traffic continues to hit the **old** project — that is
153
153
> expected during the Phase-4 setup window. Use the SAME token value the monorepo caller sends;if you
154
154
> rotate it, update it in both places: this Vercel project and the monorepo's secret that feeds
155
-
> `post-ingest.py`.
155
+
> `refresh-bench-site.py`.
156
156
157
157
> **`BENCH_DATA_TAG` is not env-configurable:** the Next.js Data Cache tag is a compile-time constant
158
158
> (`export const BENCH_DATA_TAG = 'bench-data'` in `src/bench/lib/data-cache.ts`), imported directly by
0 commit comments