-
Notifications
You must be signed in to change notification settings - Fork 18
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
Added SPDX format support in sbom scripts [CLOUDDST-24250] #163
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
Could you give the PR a more thorough description and link the relevant issues, docs etc.? There's a lot of guesswork for us here.
(Reviewed only base_images_sbom_script.py
so far)
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
If the newly added scripts are to be used in the buildah task in konflux, they need to be added to the Dockerfile as well - https://github.com/konflux-ci/build-tasks-dockerfiles/blob/main/sbom-utility-scripts/Dockerfile This means it will be part of the image that is used in the individual steps that are working with sbom in the buildah task, e.g. https://github.com/konflux-ci/build-tasks-dockerfiles/blob/main/sbom-utility-scripts/Dockerfile |
Is this work tracked internally somewhere? |
Seems that the CI did not run automatically because you are not a maintainer. I had to approve it and it seems to run now. Sorry about that. The new testcase is failing:
You can also test this locally with |
It's tracked in CLOUDDST-24250, I created the issue after I started working on this, so that's why it's not in the commit mesage |
if contains and inverse_map1.get(r) == root_element1: | ||
middle_element1 = r | ||
# if not middle_element1: | ||
# middle_element1 = root_element1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is probably left by mistake?
@chmeliik does @midnightercz need to be added to the rhtap-build namespace, so that the pipeline can be triggered from this PR? |
just needs /ok-to-test no? Huh, maybe not 😕 |
/retest |
/ok-to-test |
You could always edit the commit message and make life easier for everybody in the future, but now it is at least mentioned in the pull request. |
/ok-to-test |
911f910
to
b43582e
Compare
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please describe the problem, which this PR addresses, in detail in the commit message of 1b01170. The information may be about what is missing by current implementation, what's the purpose of adding SPDX format support, etc.
I added information about ADR describing the problem |
What can be done to get this merged? The EC team is awaiting this work to be done before proceeding with the full SPDX support. |
Currently the SPDX feature is in design phase konflux-ci/architecture#213 |
@chmeliik @zregvart I added changes from ADR in last commit + some explanatory comments. I also added test to compare merged cyclonedx and spdx to ensure they are equal (in sense of packages and purls). |
I've found no use of it anywhere |
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/test_base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/test_base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/test_base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
or set(keys) & set(cachi2_indexed_packages.keys()) | ||
) | ||
|
||
return package_is_duplicated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The whole package de-duplication approach for SPDX (the entire diff up to this function) is a bit overcomplicated and adds lots of code duplication.
Both syft and cachi2 never generate more than one purl for a package, and the purl format doesn't change between CDX and SPDX. So the deduplication logic should be identical between CDX and SPDX. The only difference should be whether we get the purl from .purl
or from .externalReferences
with .referenceType == "purl"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code duplication is intentional. Once we remove cyclonedx support, we can simply remove all non spdx related functions. If we enforce to support only one purl per package then logic could be simplified
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we enforce to support only one purl per package then logic could be simplified
yes please 🙏
filtered_packages = [] | ||
for p in syft_sbom.get("packages", []): | ||
if is_duplicate_package(p): | ||
if get_package_key(p) in cachi2_packages_map: | ||
cpackage = cachi2_packages_map[get_package_key(p)] | ||
cpackage["externalRefs"] = sorted( | ||
merge_external_refs(cpackage.get("externalRefs", []), p.get("externalRefs", [])), | ||
key=lambda x: ( | ||
x["referenceCategory"], | ||
x["referenceType"], | ||
x["referenceLocator"], | ||
), | ||
) | ||
cpackage["annotations"] = merge_annotations(cpackage.get("annotations", []), p.get("annotations", [])) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we merging the duplicated packages together for SPDX when we don't do it for CycloneDX? For CycloneDX, we simply drop the duplicated packages
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for cyclonedx if the component is duplicated it's based on purl. That means the component is duplicate for sure. With SPDX considering possibility of multiple purls, is_duplicate_package returns True even on partial match of purls. Therefore considered removal of duplicated packages as possible information loss and that's why attributes of the duplicate package are merged with existing one instead of discarding whole package
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/merge-cachi2-sboms-script/merge_cachi2_sboms.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/merge-cachi2-sboms-script/merge_cachi2_sboms.py
Outdated
Show resolved
Hide resolved
if relation["relatedSpdxElement"] in package_ids: | ||
relationships.append(_relation) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we only look at relatedSpdxElement
for document 1 when we look at both spdxElementId
and relatedSpdxElement
for document 2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because in the first doc spdxElementId can be root element and in that case even relationships pointing to removed packages would be included
sbom-utility-scripts/scripts/merge-cachi2-sboms-script/merge_cachi2_sboms.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
sbom-utility-scripts/scripts/base-images-sbom-script/app/base_images_sbom_script.py
Outdated
Show resolved
Hide resolved
440b1e7
to
7676a7b
Compare
Signed-off-by: Jindrich Luza <[email protected]>
Signed-off-by: Jindrich Luza <[email protected]>
Signed-off-by: Jindrich Luza <[email protected]>
- Added merge_syft_sboms_spdx.py
- Added format explanatory comments
Signed-off-by: Jindrich Luza <[email protected]>
Signed-off-by: Jindrich Luza <[email protected]>
Signed-off-by: Jindrich Luza <[email protected]>
Signed-off-by: Jindrich Luza <[email protected]>
- Formated test spdx files - Improved merging spdx files - Added test to compared merged cdx and spdx outputs
- Renamed middle element to root package - Added mandatory attributes to spdx elements Signed-off-by: Jindrich Luza <[email protected]>
- spdx_find_doc_and_root_package wraps spdx related code - fixed isodate generator - fixed annotator string - build deps are generated as SPDXRef-Image- instead of SPDXRef-container- - added test_main_input_sbom_spdx_with_packages Signed-off-by: Jindrich Luza <[email protected]>
7676a7b
to
14b867d
Compare
Added support of SPDX format for helper scripts manipulating SBOMs [CLOUDDST-24250]
Related to ADR 0039-spdx-support