Make it easier to run verification tests locally #99
Labels
enhancement
New feature or request
Comments
steiza
added a commit
to steiza/sigstore-conformance
that referenced
this issue
Sep 20, 2023
For sigstore#99 If you're only testing verification use-cases locally, you don't need the OIDC JWT. Signed-off-by: Zach Steindler <[email protected]>
|
Fully agreed! I saw you opened #100; thank you! |
woodruffw
pushed a commit
that referenced
this issue
Sep 21, 2023
* Make it easier to run verification test locally For #99 If you're only testing verification use-cases locally, you don't need the OIDC JWT. Signed-off-by: Zach Steindler <[email protected]> * Nicer error message for not providing arguments ``` sigstore-conformance$ pytest test --entrypoint /Users/steiza/code/steiza/sigstore-conformance/sigstore-python-conformance Please specify one of '--github-token' or '--skip-signing' sigstore-conformance$ echo $? 3 ``` Signed-off-by: Zach Steindler <[email protected]> --------- Signed-off-by: Zach Steindler <[email protected]>
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The existing instructions to run the tests locally involve using a GitHub token to get an OIDC JWT from https://github.com/sigstore-conformance/extremely-dangerous-public-oidc-beacon.
If you're only testing verification use-cases though, you don't need an OIDC JWT.
We should make it so if you run
pytest test --skip-signing ...you don't need a GitHub token, since you don't need an OIDC JWT.The text was updated successfully, but these errors were encountered: