Conversation
czpython
force-pushed
the
codex/issue-781-template-digests
branch
2 times, most recently
from
October 3, 2026 08:47
9e103d0 to
c1fbdd6
Compare
czpython
force-pushed
the
codex/issue-781-template-digests
branch
from
October 3, 2026 08:54
c1fbdd6 to
bd05e2f
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.
POST /templatesnow refreshes the base image before it selects a template. The savedbase_image_refpins the pulled registry digest, so a moved tag creates a new template and the asynchronous build uses that exact image. The pull sends the registry credentials for an image onREGISTRY_HOST. An image that no registry holds is a local build, and its image ID pins it. Docker Sandboxes also receives the refreshed base archive for hosts that use no template, once for each reference. Unused older templates follow the existing janitor policy.The request and response shapes stay unchanged; the digest is internal to the template record. Pull or store failures return 502; providers without template support return 400. The migration preserves existing template records and adds the resolved reference to the unique key. Deploy this service and run its migrations before the companion installer change at czpython/druks#810 for czpython/druks#781.
Operational limits: pulls and sbx loads complete before the POST response, so the caller timeout must cover them. A database downgrade needs duplicate digest generations removed first because the previous unique key cannot represent them. The exe provider still leaves remote registry cleanup to the registry.