github backend mismatches platform when selecting attestation
#7462
Unanswered
polarathene
asked this question in
Troubleshooting and bug reports
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
TL;DR:
githubbackend selected a mismatched*.provenance.jsonthat differs by platform (darwinwhen expectedwindows) from the selected asset (*.tar.gz). Reproduction below.MISE_GITHUB_GITHUB_ATTESTATIONSandMISE_AQUA_GITHUB_ATTESTATIONS.I've been trying mise recently, during which the switch to detect and implicitly opt-in for verifying attestations/provenance became the new default for
aquaandgithubbackends.I'm not sure if it's due to an oversight from the LLM driven development process, or PRs bypassing any additional human review (while also ignoring failing checks), but I noticed the following:
Resolved - Not a bug
Can be ignored mise docs are clear on when attestation doesn't apply (dependent upon the upstream aqua
registry.yamlfor a package to configure).aquabackend: No errors thrown here, but the logs show onlycontainerdwas verifying,buildkitwas skipped from verifying attestations (even when it was the only asset to install).Different discovery logic I assume 🤷♂️ (EDIT: Confirmed, the equivalent BuildKit
registry.yamllacks agithub_artifact_attestationsfield, hence no verification)Github Actions log output (aqua backend)
githubbackend: For some reason it's resolving the wrong provenance (buildkit-v0.26.3.darwin-amd64.provenance.json) to verify against the binary asset selected? (buildkit-v0.26.3.windows-amd64.tar.gz)Github Actions log output (github backend)
I am aware of the opt-out via
MISE_GITHUB_GITHUB_ATTESTATIONSandMISE_AQUA_GITHUB_ATTESTATIONSenvironment vars, although I'm curious why there isn't a backend agnostic ENV 🤔Reproduction
Github Actions workflow:
Beta Was this translation helpful? Give feedback.
All reactions