Pin SCV staging secret versions

d424f89e8cb9 · AtlantisPleb · 9d ago · parent b28e76eaf5c1

Pin SCV staging secret versions

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Not deployed through the forge lane

No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.

Changed files

modified docs/operations/scv-staging-qualification.md

Diff

1 file changed, +2 -2

   - `SCV_TIMEOUT_MS` and `SCV_HEARTBEAT_INTERVAL_MS` with bounded values.
   - `SCV_DIAGNOSTIC_LOGS=false`.

5. Map `OPENAI_API_KEY` from the staging secret at runtime. Do not print or
   persist its value.
5. Map `OPENAI_API_KEY` from a specific enabled numeric version of the staging
   secret at runtime. Do not use `latest`, print the value, or persist it.
6. Execute one job task and wait for its terminal state.

## Verify the execution

47	47		- `SCV_TIMEOUT_MS` and `SCV_HEARTBEAT_INTERVAL_MS` with bounded values.
48	48		- `SCV_DIAGNOSTIC_LOGS=false`.
49	49
50		-	5. Map `OPENAI_API_KEY` from the staging secret at runtime. Do not print or
51		-	`persist its value.`
	50	+	5. Map `OPENAI_API_KEY` from a specific enabled numeric version of the staging
	51	+	secret at runtime. Do not use `latest`, print the value, or persist it.
52	52		`6. Execute one job task and wait for its terminal state.`
53	53
54	54		`## Verify the execution`