Skip to content

codegen-orchestrator-1713: Skip unchanged deploy-owned secret payloads - #853

Merged
vladmesh merged 2 commits into
mainfrom
pipeline/codegen-orchestrator-1713
Oct 19, 2026
Merged

vladmesh merged 2 commits into
mainfrom
pipeline/codegen-orchestrator-1713

Conversation

@vladmesh

Copy link
Copy Markdown
Owner

What

Candidate: branch pipeline/codegen-orchestrator-1713, commit 14b0f5c (tree dacfc1988c8bb3bd02f544907f739f447a558b26), based on main 9f24567. One commit, no AI trailer, TASK.md not committed. git status --porcelain is empty.

Why

Skip unchanged writes of the six deployer-owned GitHub secrets using a successful-payload digest retained across deploy jobs. This is the next independently mergeable d6 increment of sprint1496. The three REGISTRY_* secrets stay on their current refresh path in this increment; d6 remains open until their shared-writer boundary is handled separately.

How verified

CI runs Backend Docker-in-Docker Integration Tests, Build Service Image Candidates, Build Worker Base Image Candidates, CI Contract, Detect Changed Services, Fast Checks (Unit Tests), Lint (Ruff), Publish Service Image Release, Publish Worker Base Images, Required CI Gate, Service Image Entrypoint Imports on 14b0f5c2d611; the merge waits for them to pass.

Card: codegen-orchestrator-1713

… receipt

A deploy digests the GitHub repository id and its six deployer-owned secret
values. A matching receipt from an earlier complete write skips those six PUTs
and their public-key reads; REGISTRY_* are still written on every deploy. The
receipt is claimed (hit or deleted) and published in Lua scripts that compare
the project deploy lock first, and published only after all nine secrets were
set. Every secret PUT attempt, retries included, checks the lock through the
shared request guard, and a refusal stops the batch as DeployFenceLost.
@vladmesh
vladmesh merged commit 835bf38 into main Oct 19, 2026
26 checks passed
@vladmesh
vladmesh deleted the pipeline/codegen-orchestrator-1713 branch October 19, 2026 06:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant