chore(image): give the rust recipe its own immutable alias - #316
Merged
Conversation
#315 changed what the image contains and left every alias where it was, so the build refused: b18 already exists and points at the promoted image, with the previous recipe digest recorded on it. That refusal is the immutability contract working. An alias names one set of bytes, and reusing it for a different recipe would make the estate's audit describe an image that no longer exists under that name. All four aliases advance together -- container b18 to b19, container integration b11 to b12, integration b14 to b15, standard b15 to b16 -- so a later rebuild of any variant does not hit the same refusal one at a time. The two pinned fingerprints move with them.
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.
#315changed what the image contains and left every alias where it was, so the build refused:That refusal is the immutability contract working.
b18already exists and points at fingerprint7f427030…— the image currently promoted ascurrent— with the previous recipe digest recorded on it. An alias names one set of bytes; reusing it for a different recipe would make the estate's audit describe an image that no longer exists under that name.All four aliases advance together rather than one at a time, so a later rebuild of any variant does not hit the same refusal again:
The two pinned fingerprints move with them: recipe
3d89d31c…, manifest02591ff0….Found while building the image on a drained
gha-runner-2— the member the estate's two previous stage audits also used.