-
Notifications
You must be signed in to change notification settings - Fork 137
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
Using UUID Output from “generator/Create and sign provenance” Step in generator_generic_slsa3 Job #3741
Comments
You would have to modify the workflow to save the command output as Step, Job, and Workflow outputs. We would welcome a PR. From
And set the output like this |
Can you tell us more about your use-case for outputting the rekor UUID as a workflow output? |
We need to search for unique logs in sigstore using the rekor entry UUID to verify provenance. Using the hash alone isn't enough to identify the provenance generated by the current workflow, especially if the deployment fails or multiple people deploy the same code. Therefore, the rekor Entry UUID as a workflow output is crucial to accurately identify the generated provenance. |
For Sigstore, we want to discourage doing live lookups in the log in favor of verifying persisted inclusion proofs offline. We've filed an issue (#3750) to track support for this. In the meantime, adding the Rekor entry UUID as output seems reasonable. |
Closing due to inactivity. |
When using generator_generic_slsa3 in the workflow, the last part of the "generator/Create and sign provenance" step outputs "Uploaded signed attestation to rekor with UUID". I would like to use this UUID value as input in a subsequent job. How should I do this?
The text was updated successfully, but these errors were encountered: