feat: prepare Cloud admissions from attested hosted evidence - #46
Merged
Merged
Conversation
Signed-off-by: abrichr <richard.abrich@mldsai.com>
Signed-off-by: abrichr <richard.abrich@mldsai.com>
Signed-off-by: abrichr <richard.abrich@mldsai.com>
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.
The measured admission preparer currently accepts Flow releases only. This change adds a Cloud entry point that verifies a hosted campaign's retained evidence and exact deployment before preparing the existing admission objects.
The Cloud adapter verifies the fixed private producer's GitHub attestation, opens the committed evidence files, derives the campaign counters, and checks the protected deployment run and provider identities. A separate attested observation can supply a fresh publication time while preserving the original campaign bytes. The default Flow executable still selects Flow from its verified artifact inventory.
Published deployments also need verification receipts without a GitHub draft release ID. The schema and receipt writer now support that deployment case; package and hybrid releases still require the ID. The extracted GitHub attestation verifier retains the existing signature and identity checks.
Preparation is unsigned by default. This PR changes verification code and synthetic tests; actual Cloud execution and admission evidence remain pending.
Validation: all 370 repository tests pass with the existing test environment and read-only PyPI access. The actual collector and observer's offline output passes the Cloud adapter unchanged; altered identities for each of the three runner functions are rejected. That interface check uses synthetic provider data and stubs provenance authentication, which the separate attestation tests cover.
Opened by an agent session, not the founder.