-
-
Notifications
You must be signed in to change notification settings - Fork 86
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
Make name of attached artifact configurable (and hence support multi-bom projects) #483
Comments
For this and other use cases - would it be possible to support the configuration settings also as command line options? |
oh, both separate test and runtime SBOMs requirements: it seems we now have a use case for #433 @lfvjimisola in that case, what would you configure for the 2 runs, so we share complete example? |
That's great news. Of course, my team member @lfvJonas will provide one here today. |
This is the configuration we have.
|
Due compliance we need to provide a runtime SBOM and a test SBOM and have them attached during install/deploy.
However,
which results in
[WARNING] artifact x:y:json:cyclonedx:0.8.15-SNAPSHOT already attached, replace previous instance
The name of the artifact for the SBOM artifact needs to be configurable on per-SBOM basis (it's currently hard-coded) within the
<configuration>
section in addition to<outputName>
.The text was updated successfully, but these errors were encountered: