fix: use base64 output file for provenance for large assets #7496
Conversation
This file contains 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
jackkav
approved these changes
Jun 5, 2024
filfreire
approved these changes
Jun 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
GH jobs redacts base64 encoded string of large assets and might contain secrets. There is no way to pass the encoded digest as job outputs for provenance.
Failed workflow: https://github.com/Kong/insomnia/actions/runs/9383289942/job/25836570705#step:8:49 with digest redacted leading to send failed job output considered sensitive
Issue: https://github.com/orgs/community/discussions/37942
Solution:
Refer https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/generic/README.md#getting-started