Repository navigation
ci: add protected encrypted warm snapshot reader - #985
Conversation
|
@codex review Please review the exact current head recorded below, including all four changed files, protected Environment boundaries, GET-only provider transport, encrypted-only export, receipt bindings, drift handling and failure diagnostics. This is a Draft-only change; no operational dispatch or merge is requested. Exact head: 3846f9f |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Can't wait for the next one! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
What changed
Add
read-warm-recovery-snapshot.yml, a manual main-only read-only workflow behind the existing protected Environment. Reuse WIF for GET-only Resource Manager, Cloud Run and exact bootstrap-object reads. Verify stable target snapshots and receipt/card bindings; export only authenticated CMS AES-256-GCM ciphertext for the coordinator. The reader supplies live bootstrap fields without invoking bootstrap or recovery.Protected reader configuration and a trusted coordinator encryption certificate are separate prerequisites. This PR provisions neither. The retained recovery operator is unchanged. No cloud mutation, workflow dispatch, Secret/IAM write, deployment, PAPER, live, Kelly or stop-loss activation is authorized or performed. Leave this PR Draft for the established review-and-merge bot.
How verified
AI assistance
Implemented and locally self-reviewed with OpenAI Codex (gpt-6.1-sol, medium reasoning; configured by the job runner). Independent review is requested from the established Codex review service on this exact head; its result is pending.
Publication scan
publication-check/2.0-advisory(build83d9d1130377), advisory exit 0: full tracked tree 2582 findings / 2457 matching lines. Pre-new-file inventory: 2581 findings / 2456 lines; the added finding is public OIDC permission syntax. The changed-files/artifact scan found 25 lines in two files: existing rollout documentation and public workflow permission syntax; no reader/test matches. No real credential or new target binding was found in the added source. The central public runtime configuration scan passed with zero matches. No scanner enforcement or repository gate was changed.First 20 matches (shared-masked text):