Repository navigation
DRU-774 -- Lead each template image tag with its label - #72
Merged
Merged
Conversation
czpython
changed the title
czpython
force-pushed
the
readable-template-tags
branch
from
October 11, 2026 09:37
eb17294 to
861ad27
Compare
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.
A template image tag now starts with the caller's label, then the content hash:
ghcr.io/acme/sandbox-templates:site-builder-build-3fa9c1d2e4b7, notghcr.io/acme/sandbox-templates:3fa9c1d2e4b7. The registry then shows which app each template belongs to.Drukbox lowercases the label and replaces every run of other characters with a hyphen. It keeps at most 115 characters, so the tag stays inside the 128-character limit. A template with no label keeps the hash alone.
The hash still names the build, so a repeated build of the same base and script gets the same tag. Template reuse is unchanged: provider, base image reference, and script hash. Two templates that share a script and base carry the label of the request that created the record.