You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if you could override or set the version of the main component when you do sbomasm assemble -v [X.Y.Z] -c [config]. This allows you to set default in config but make them specific in your CI for example base on input variables.
The text was updated successfully, but these errors were encountered:
Current functionality:
We can override the default values from the config file, but there’s a strict requirement to provide all three values in the group: "name," "type," and "version." If we try to override just one value (e.g., "version"), the command enforces providing the other two values as well, which is restrictive.
For example:
$ sbomasm assemble -v "v1.0.20" -c config.yaml -o final-sbom-config.spdx.json sbomex-cdx.json sbomgr-cdx.json
Error: if any flags in the group [name version type] are set they must all be set; missing [name type]
Our desired functionality is:
When a config.yaml file is provided, users should have the flexibility to override any individual field (e.g., just "version") without being required to provide all the other grouped fields.
It would be great if you could override or set the version of the main component when you do
sbomasm assemble -v [X.Y.Z] -c [config]
. This allows you to set default in config but make them specific in your CI for example base on input variables.The text was updated successfully, but these errors were encountered: