-
Notifications
You must be signed in to change notification settings - Fork 30
feat!: allow specifying the dependency depth resolution through CLI and make dependency resolution off by default #840
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
feat!: allow specifying the dependency depth resolution through CLI and make dependency resolution off by default #840
Conversation
a2d2f9c to
f2dde1f
Compare
tests/integration/cases/apache_maven_sbom_with_no_deps_resolution/sbom.json
Show resolved
Hide resolved
f2dde1f to
ab375ee
Compare
7d2ab75 to
ac7639e
Compare
behnazh-w
left a comment
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 --skip-deps option is still mentioned in the usage documentation and various tutorials. Could you please remove these references and ensure that the remaining text remains clear and coherent?
…d allow to provide it as argumentto dependency resolver
…deps resolution by default
…th the Sphinx documentation
… treated as error
ac7639e to
8b6ceac
Compare
I have removed the remaining |
…nd make dependency resolution off by default (#840) Signed-off-by: Trong Nhan Mai <trong.nhan.mai@oracle.com>
Closes #838 .
In this Pull Request I made the following changes:
defaults.iniconfiguration.--skip-depsan no-op. I also added--deps-depthas a new flag for setting the dependency resolution behavior (it's disabled by default).--deps-depth:--deps-depth--deps-depthwhen providing SBOM or Python Virtual Environment as input.