Create SBOM using Syft #134
Merged
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
This is just a placeholder that should be replaced later with actual sbom content of this project Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
This commit makes it ready for a pull request, it will only trigger on a release build for now. It should also be noted that this workflow currently still uses a temporary SBOM SPDX, a new pull request should be created to generate the SBOM Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Codecov Report
@@ Coverage Diff @@
## main #134 +/- ##
=======================================
Coverage 77.54% 77.54%
=======================================
Files 15 15
Lines 610 610
=======================================
Hits 473 473
Misses 97 97
Partials 40 40
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
marcofranssen
requested changes
Feb 9, 2022
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Closed
JeroenKnoops
previously approved these changes
Feb 10, 2022
marcofranssen
requested changes
Feb 10, 2022
Yaml formatting and cosign{-installer} version
Signed-off-by: Brend Smits <brend.smits@philips.com>
…ovenance-Action into feature/create-sbom
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
marcofranssen
requested changes
Feb 17, 2022
… it getting stuck Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Brend-Smits
force-pushed
the
feature/create-sbom
branch
from
e5a1afd
to
7bc5302
Compare
Signed-off-by: Brend Smits <brend.smits@philips.com>
Signed-off-by: Brend Smits <brend.smits@philips.com>
Brend-Smits
force-pushed
the
feature/create-sbom
branch
from
287b3eb
to
30cbe62
Compare
|
https://github.com/philips-labs/slsa-provenance-action/runs/5235719140?check_suite_focus=true |
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.
The SBOM is created using tooling from Anchore, called Syft. Syft was chosen because of the ease of use and the good integration with our tech stack.
I think this could have been a separate step in the workflow, but in the end, I chose not to go this route. The reason being is that it will be a lot of repeating the same code and will raise a new problem that we have to upload a temporary artifact or pass along a different output (which may have issues being passed around since the SBOM's can be relatively large in size).
This PR also removes the filter sbom spdx.