{{ message }}
ROX-30569: Add SBOM Scanning REST API to Central#18484
Merged
Merged
Conversation
4eaf9ae to
5993fc8
Compare
Contributor
|
Images are ready for the commit at 09f9e5f. To use with deploy scripts, first |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #18484 +/- ##
==========================================
- Coverage 49.52% 49.50% -0.02%
==========================================
Files 2666 2667 +1
Lines 201181 201389 +208
==========================================
+ Hits 99629 99698 +69
- Misses 94115 94249 +134
- Partials 7437 7442 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
5993fc8 to
9749407
Compare
9a425e2 to
1aa7166
Compare
BradLugo
reviewed
Jan 16, 2026
1aa7166 to
be324f8
Compare
Contributor
Author
|
Rebased from master, expecting that to address the prior unrelated UI errors |
971c703 to
2643358
Compare
2643358 to
01e65a6
Compare
Contributor
Author
|
Rebased to address conflicts |
This was referenced Jan 23, 2026
This was referenced Jan 27, 2026
BradLugo
approved these changes
Feb 13, 2026
So that it is easier to differentiate between the the generation vs. scanning handler.
- HTTP handler - Pass http request reader to Scanner V4 integration - Mock conversion of vuln report to Scan SBOM response
- made 'getScannerV4SBOMIntegration' reusable from SBOM gen and scan - now pass request context down to scannerv4 client - read size exceeds limit from error directly - removed operating system variable from the sbom response type
01e65a6 to
09f9e5f
Compare
Contributor
Author
This file contains hidden or 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
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.

Description
Adds the
/api/v1/sboms/scancustom route and handler to facilitate SBOM scanning. Reading the SBOM content from the request and scanning it will be handled in a future PR - a fake response is returned for now.A few decisions to call out (happy to change as needed):
ROX_SBOM_SCANNINGROX_SBOM_MATCHING- I'm happy to change it, the API endpoint hasscanin its path and other user exposed areas of ACS reference 'scanning' - 'SCAN' seemed like the more consistent value.File sizes from: https://security.access.redhat.com/data/sbom/v1/spdx/
PR Stack:
User-facing documentation
Testing and quality
Automated testing
How I validated my change
Unit tests + sending a fake request to the API:
Max request size enforcement