Adopt separate registry and template settings after the Drukbox update - #434
Draft
czpython wants to merge 1 commit into
Draft
Adopt separate registry and template settings after the Drukbox update#434czpython wants to merge 1 commit into
czpython wants to merge 1 commit into
Conversation
This was referenced Sep 5, 2026
czpython
force-pushed
the
codex/shared-template-registry
branch
from
September 5, 2026 11:40
6b1d667 to
493bba2
Compare
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
czpython
force-pushed
the
codex/registry-contract-follow-up
branch
from
September 5, 2026 11:44
9f1b546 to
c90474c
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.
What changed
Configure general private image access in
[registry]and the shared template destination in[templates]. Registry credentials work without a template repository. All providers receive the new Drukbox settings from one source. Provider tables and[env]cannot override them.App declarations and template SDK requests stay unchanged. Document the new registry contract and image tags with digest references.
Risk
Future follow-up. Requires czpython/drukbox#28 before activation. The current production Drukbox does not read these generic keys. Replace the exe-specific registry keys with the new tables when adopting that release. No database migration or SDK change. Keep this draft separate from the current deployment.
Verification
uv run ruff check backend: passed after rebase.uv run ruff format --check backend: passed after rebase.uv run pytest backend/tests/test_setup_env.py backend/tests/test_declared_sandboxes.py -q: 49 passed after rebase.main.