build-push-to-dockerhub: Generate SBOM & attestations #120
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.
This generates an SBOM and attestations for that SBOM and also build provenance. These are also stored in one of GitHub's SigStore instances, so the provenance of images built using this action can be verified.
We do this by repurposing the
syft-sbom-report
action and calling that as a nested composite action, to encapsulate the generation and pushing work. This wasn't a usable action (noaction.yaml
) anyway. It was already referencing theanchore/sbom-action
we use here.