-
Notifications
You must be signed in to change notification settings - Fork 112
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
Add launcher SBOM input #963
Conversation
Signed-off-by: Natalie Arellano <narellano@vmware.com>
Signed-off-by: Natalie Arellano <narellano@vmware.com>
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.
I loved how simply is adding a new flag after the refactoring! Great Job @natalieparellano
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #963 +/- ##
==========================================
- Coverage 64.54% 64.44% -0.10%
==========================================
Files 86 86
Lines 6175 6171 -4
==========================================
- Hits 3985 3976 -9
- Misses 1813 1820 +7
+ Partials 377 375 -2
Flags with carried forward coverage won't be shown. Click here to find out more. |
Sigh... again I think Codecov is being too picky (the newly exported constants are being tested implicitly elsewhere). @jabrown85 do you have an opinion? |
I'm fine with it! |
As a follow on to #944, this PR introduces a
-launcher-sbom
flag to the exporter & creator so that users who supply their own launcher can supply an SBOM for that launcher.Related spec PR: https://github.com/buildpacks/spec/pull/332/files?diff=split&w=1