-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add sigstore signing integration test #324
Conversation
This could also be moved to the higher API level now that #323 is merged |
+1, let's migrate both this and the benchmarks to the higher level API |
I'll note there is a lot of variance in runtime depending on the GitHub action scheduling in the conformance repo, I've seen anything from 4s to 3m. So we could have this as a check on every PR (maybe not required?), or set it up on a schedule. |
By default `hatch test` wont run integration tests, but they can be run with `hatch test -m integration`. Signed-off-by: Spencer Schrock <[email protected]>
Signed-off-by: Spencer Schrock <[email protected]>
Signed-off-by: Spencer Schrock <[email protected]>
matrix: | ||
os: [ubuntu-latest, macos-latest, windows-latest] | ||
python-version: ['3.10', '3.11', '3.12', '3.13'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can make this a smaller matrix if desired (currently 12 signing + verifying events per PR update), I know we talked about other OS test properties that may need to be manual. (sign on linux, verify on windows)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Summary
With the addition of #319, we can test OIDC signing more easily using Sigstore's extremely dangerous public OIDC beacon.
This is the first integration tests and relates to #5. The change is written such that
hatch test
will continue to only run unit tests. Devs and CI jobs that want to run the integration tests need to use theintegration
marker:I'm still playing with the test, particularly around handling of expired tokens.
Release Note
NONE
Documentation