Configure exe sandbox templates with the existing Drukbox contract - #433
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
czpython
force-pushed
the
codex/shared-template-registry
branch
from
September 5, 2026 11:40
6b1d667 to
493bba2
Compare
czpython
enabled auto-merge (squash)
September 5, 2026 11:41
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
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
Expose the registry values that the existing exe provider needs to publish sandbox templates. Fresh exe installs now show blank EXE_IMAGE_REGISTRY, EXE_REGISTRY_USERNAME, and EXE_REGISTRY_PASSWORD entries in
[sandbox.exe]. The existing renderer passes configured values through unchanged. One full repository holds all templates.Send readable app/script labels through the existing template API; template reuse remains based on content. No public documentation changes.
Risk
This PR works with the current Drukbox contract. It has no dependency on the future Drukbox registry changes. Operators must supply the registry values and recreate Drukbox with its existing image. The PR alone does not configure production credentials or rebuild an existing failed template.
No database migration, SDK change, or Drukbox image update. The future drafts are Drukbox czpython/drukbox#28 and Druks #434. Neither blocks this PR.
To unblock the deployment, set these values in the existing
[sandbox.exe]table:Render
.env, recreate Drukbox with its current image, delete the failed template through its API, then rundruks doctor.Verification
uv run ruff check backend: passed.uv run ruff format --check backend: passed.uv run pytest backend/tests/test_setup_env.py backend/tests/test_declared_sandboxes.py -q: 46 passed.uv pip install -e backend/tests/druks-field_notesbefore the full backend run.uv run pytest backend/ -q: 1,584 passed, 19 warnings.