Skip to content

Conversation

sethmlarson
Copy link
Contributor

@sethmlarson sethmlarson commented Jan 12, 2024

Part 1 of #2339

I modeled this PR off of the Sigstore bundle PR since it's a very similar approach.

There may be more than one SBOM per artifact eventually (for multiple reasons, either users demanding CycloneDX or a new major version of SPDX) so accounting for that possibility by using spdx2 as the prefix for the database field.

I don't know what the "admin" interface needs to look like for release managers to be able to submit SBOM files for new releases, this might already be enough if Sigstore bundles are doable today.

@hugovk
Copy link
Member

hugovk commented Jan 12, 2024

Updating from main should fix the Read the Docs build.

@sethmlarson
Copy link
Contributor Author

@hugovk Thanks Hugo! I've rebased on main.

@sethmlarson
Copy link
Contributor Author

Okay I believe that by adding the sbom_spdx2_file field to ReleaseFileResource is enough to add support for uploading via API. This will require a change in python/release-tools#82 once it's available here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants