feat(pin-gate): auto-pin chronicle image digests#322
Merged
Conversation
…3-safe bot-token push)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Auto-pin chronicle image digests on the chart pin-gate: for same-repo PRs it resolves each changed chart's
.image(the standardimage.repository+image.tagshape) to its multi-arch index digest, writes the pin intovalues.yaml, and pushes ONEci: auto-pin chronicle image digestscommit to the PR branch with the Chronicle bot App token (which re-triggers the gate -> green). No manual pinning, no "apply suggestion" loop.Notes
helm templaterender-flag stays the verdict; the auto-pin only handles the standardimage.repository+image.tagshape, so any non-standard or unresolvable image is still flagged for a manual pin.origin(no extraheader clash). Mint iscontinue-on-errorand the push is gated on a non-empty token, so a transient mint failure or a fork PR (secrets withheld) can never block the required gate -- those keep the flag-only behaviour.spire:0.68.3-> auto-pinned to@sha256:79df4fb2...+ pushed by the bot, no 403, re-run green). Test PR closed.