M0.12: enforce verified deployment paths - #15
Merged
Merged
Conversation
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.
Implements M0.12 deployment enforcement on top of M0.11 verification.
Changes:
compose.yamlto consume an immutable verified image viaGLOWING_BEAR_IMAGE;scripts/deploy-verified-compose.sh, which verifies the release first, pulls only the immutable digest, validates Compose, and starts with--no-build;scripts/render-verified-quadlet.sh, which emits a Quadlet only after verification and pinsImage=to the immutable digest;Deployment enforcementCI that exercises a real signed release (v0.2.3), verifies the running Compose container uses an immutable digest, checks/healthz, and validates Quadlet output;docs/M0_12_DEPLOYMENT_ENFORCEMENT.md.This intentionally does not claim host-wide Docker/Podman admission control; it enforces the repository's supported secure deployment paths.