Skip to content
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

docs: synchronizing README from GitBook #5063

Merged
merged 1 commit into from
Mar 13, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion help/cli-commands/container-sbom.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ Required. The image for which you will generate an SBOM document.

### Create a SPDX JSON document for an image while excluding application dependencies

`$ snyk container sbom --format=spdx2.3+json redis:latest ----exclude-app-vulns`
`$ snyk container sbom --format=spdx2.3+json redis:latest --exclude-app-vulns`

### Refer to a container image by its digest

Expand Down
8 changes: 4 additions & 4 deletions help/cli-commands/monitor.md
Original file line number Diff line number Diff line change
Expand Up @@ -221,13 +221,13 @@ This is an alias for `--project-tags`

### `--maven-aggregate-project`

Use `--maven-aggregate-project` instead of `--all-projects` when scanning Maven aggregate projects, that is, ones that use modules and inheritance.
Use `--maven-aggregate-project` instead of `--all-projects` when scanning Maven aggregate projects, that is, projects that use modules and inheritance.

When scanning these types of projects, Snyk performs a compile to ensure all modules are resolvable by the Maven reactor.
Using `--maven-aggregate-project` instructs Snyk to perform a compilation step to ensure all modules within the project are resolvable by the Maven reactor. This ensures a comprehensive scan that includes dependencies of all sub-modules.

Be sure to run the scan in the same directory as the root pom.xml file.
Be sure to run the scan in the same directory as the root `pom.xml` file.

Snyk reports test results per pom.xml file.
Snyk reports the test results per individual `pom.xml` file within the aggregate project.

### `--scan-unmanaged`

Expand Down
8 changes: 4 additions & 4 deletions help/cli-commands/test.md
Original file line number Diff line number Diff line change
Expand Up @@ -224,13 +224,13 @@ To fail on any Snyk-discoverable vulnerability (the default behavior), do not us

### `--maven-aggregate-project`

Use `--maven-aggregate-project` instead of `--all-projects` when scanning Maven aggregate projects, that is, ones that use modules and inheritance.
Use `--maven-aggregate-project` instead of `--all-projects` when scanning Maven aggregate projects, that is, projects that use modules and inheritance.

When scanning these types of projects, Snyk performs a compile to ensure all modules are resolvable by the Maven reactor.
Using `--maven-aggregate-project` instructs Snyk to perform a compilation step to ensure all modules within the project are resolvable by the Maven reactor. This ensures a comprehensive scan that includes dependencies of all sub-modules.

Be sure to run the scan in the same directory as the root pom.xml file.
Be sure to run the scan in the same directory as the root `pom.xml` file.

Snyk reports test results per pom.xml file.
Snyk reports the test results per individual `pom.xml` file within the aggregate project.

### `--scan-unmanaged`

Expand Down
Loading