docs: synchronizing help from snyk/user-docs

Author: chdorner-snyk

help/cli-commands/README.md

@@ -44,7 +44,7 @@ Commands to find and manage security issues in Infrastructure as Code files.
 
 Find security issues using static code analysis.
 
-### [`snyk sbom`](sbom.md) <a href="#snyk-sbom" id="snyk-sbom"></a>
+### [`snyk sbom`](sbom.md)
 
 Produce an SBOM for a local software project in an ecosystem supported by Snyk.
 

help/cli-commands/code-test.md

@@ -45,7 +45,7 @@ Default: `<ORG_ID>` that is the current preferred organization in your [Account
 
 Note that you can also use `--org=<orgslugname>`. The `ORG_ID` works in both the CLI and the API. The organization slug name works in the CLI, but not in the API.
 
-For more information see the article [How to select the organization to use in the CLI](https://support.snyk.io/hc/en-us/articles/360000920738-How-to-select-the-organization-to-use-in-the-CLI)
+For more information see the article [How to select the organization to use in the CLI](https://docs.snyk.io/snyk-cli/test-for-vulnerabilities/how-to-select-the-organization-to-use-in-the-cli)
 
 ### `--json`
 

help/cli-commands/iac-capture.md

@@ -0,0 +1,84 @@
+# IaC capture
+
+## Usage
+
+**Feature availability:** This feature is available in Snyk CLI version v1.1117.0 or greater.
+
+`snyk iac capture [<OPTIONS>] [<PATH>]`
+
+## Description
+
+The `snyk iac capture` command generates a mapping artifact that contains the minimum amount of information needed to generate, from Terraform state files, resource mappings from code to Cloud, such as resource IDs and names, and sends the mapping artifact to Snyk.
+
+Snyk uses this information to link Cloud issues to their originating IaC files. The links can be viewed in the Snyk Web UI.
+
+For more information, see [Fix Cloud issues in IaC](https://docs.snyk.io/scan-cloud-deployment/snyk-cloud/snyk-cloud-issues/fix-cloud-issues-in-iac)
+
+For a list of related commands see the [snyk iac](iac.md) help; `iac --help`
+
+## Exit codes
+
+Possible exit codes and their meaning:
+
+**0**: success\
+**1**: failed to capture one or more Terraform states
+
+## Configure the Snyk CLI
+
+You can use environment variables and set variables for connecting with the Snyk API; see [Configure the Snyk CLI](https://docs.snyk.io/snyk-cli/configure-the-snyk-cli)
+
+## Debug
+
+Use the `-d` option to output the debug logs.
+
+## Options
+
+### `--org=<ORG_ID>`
+
+Specify the `<ORG_ID>` to run Snyk commands tied to a specific organization. Overrides the default `<ORG_ID>` that is the current preferred organization in your [Account settings](https://app.snyk.io/account)
+
+Note that you can also use `--org=<orgslugname>`. The `ORG_ID` works in both the CLI and the API. The organization slug name works in the CLI, but not in the API.
+
+For more information see the article [How to select the organization to use in the CLI](https://docs.snyk.io/snyk-cli/test-for-vulnerabilities/how-to-select-the-organization-to-use-in-the-cli)
+
+### `--stdin`
+
+Generate the mapping artifact from Terraform state in the standard input instead of looking for state files in the `PATH`.
+
+```
+$ terraform pull | snyk iac capture --stdin
+```
+
+### `PATH`
+
+Optional argument to generate the mapping artifact from Terraform state file(s) in the PATH. Can either be a path to a directory, a path to a file, or a glob pattern.
+
+```
+$ snyk iac capture /path/to/states/**/*.tfstate
+```
+
+## Examples for snyk iac capture command
+
+### Capture from all states in the current working directory
+
+```
+$ snyk iac capture
+```
+
+### Capture from all files ending with .tfstate in a directory
+
+```
+$ snyk iac capture /path/to/states/**/*.tfstate
+```
+
+### Capture from a single state file
+
+```
+$ snyk iac capture /path/to/state.tfstate
+```
+
+### Capture from states pulled with Terraform in the standard input
+
+```
+$ terraform pull | snyk iac capture --stdin
+```

help/cli-commands/iac-describe.md

@@ -62,7 +62,7 @@ Specify the `<ORG_ID>` to run Snyk commands tied to a specific organization. Ove
 
 Note that you can also use `--org=<orgslugname>`. The `ORG_ID` works in both the CLI and the API. The organization slug name works in the CLI, but not in the API.
 
-For more information see the article [How to select the organization to use in the CLI](https://support.snyk.io/hc/en-us/articles/360000920738-How-to-select-the-organization-to-use-in-the-CLI)
+For more information see the article [How to select the organization to use in the CLI](https://docs.snyk.io/snyk-cli/test-for-vulnerabilities/how-to-select-the-organization-to-use-in-the-cli)
 
 ### `--from=<STATE>[,<STATE>...]`
 

help/cli-commands/iac.md

@@ -15,7 +15,8 @@ For more information see [Snyk CLI for Infrastructure as Code](https://docs.snyk
 All the `snyk iac` commands are listed here with the help options:
 
 - [iac test](iac-test.md); `iac test --help`: tests for any known security issue
-- [iac update-exclude-policy](iac-update-exclude-policy.md); `iac update-exclude-policy --help`: auto-generates `.snyk` exclusions for cloud resources\
-  Example: `snyk iac describe --json --all | snyk iac update-exclude-policy`
+- [iac capture](iac-capture.md); `iac capture --help`: generates mapping artifacts by accessing Terraform state configurations 
 - [iac describe](iac-describe.md); `iac describe --help`: detects infrastructure drift and unmanaged cloud resources\
   Example: `snyk iac describe --only-unmanaged`
+- [iac update-exclude-policy](iac-update-exclude-policy.md); `iac update-exclude-policy --help`: auto-generates `.snyk` exclusions for cloud resources\
+  Example: `snyk iac describe --json --all | snyk iac update-exclude-policy`

help/cli-commands/monitor.md

@@ -110,7 +110,7 @@ Default: `<ORG_ID>` that is the current preferred organization in your [Account
 
 Note that you can also use `--org=<orgslugname>`. The `ORG_ID` works in both the CLI and the API. The organization slug name works in the CLI, but not in the API.
 
-For more information see the article [How to select the organization to use in the CLI](https://support.snyk.io/hc/en-us/articles/360000920738-How-to-select-the-organization-to-use-in-the-CLI)
+For more information see the article [How to select the organization to use in the CLI](https://docs.snyk.io/snyk-cli/test-for-vulnerabilities/how-to-select-the-organization-to-use-in-the-cli)
 
 ### `--file=<FILE>`
 
@@ -310,7 +310,7 @@ You can specify how many sub-directories to search using `--detection-depth`.
 
 You can exclude directories and files using `--exclude`.
 
-Default:`--all-projects` automatically detects and scans Yarn Workspaces.with other projects.&#x20;
+Default:`--all-projects` automatically detects and scans Yarn Workspaces.with other projects.
 
 ## Option for CocoaPods projects
 
@@ -352,7 +352,7 @@ Add`--package-manager=pip` to your command if the file name is not `requirements
 
 This option is mandatory if you specify a value for the `--file` parameter that is not to a `requirements.txt` file. The test fails without this parameter. Specify this parameter with the value `pip`.
 
-For complete information about the command see [`--package-manager=<PACKAGE_MANAGER_NAME>`](https://docs.snyk.io/snyk-cli/commands/monitor#package-manager-less-than-package_manager_name-greater-than)``
+For complete information about the command see [`--package-manager=<PACKAGE_MANAGER_NAME>`](https://docs.snyk.io/snyk-cli/commands/monitor#package-manager-less-than-package_manager_name-greater-than)\`\`
 
 ## Options for scanning using `--unmanaged`
 

help/cli-commands/sbom.md

@@ -6,7 +6,7 @@
 
 **Note:** In order to run the SBOM generation feature, you must use a minimum of CLI version 1.1071.0.
 
-`$ snyk sbom --format=<cyclonedx1.4+json|spdx2.3+json|cyclonedx1.4+xml> [--file=<file>] [--unmanaged] [--org=<ORG_ID>] [<TARGET_DIRECTORY>]`
+`$ snyk sbom --format=<cyclonedx1.4+json|cyclonedx1.4+xml>|spdx2.3+json [--file=<file>] [--unmanaged] [--org=<ORG_ID>] [<TARGET_DIRECTORY>]`
 
 ## Description
 

help/cli-commands/test.md

@@ -107,7 +107,7 @@ Default: `<ORG_ID>` that is the current preferred organization in your [Account
 
 **Note:** You can also use `--org=<orgslugname>.` The `ORG_ID` works in both the CLI and the API. The organization slug name works in the CLI, but not in the API.
 
-For more information see the article [How to select the organization to use in the CLI](https://support.snyk.io/hc/en-us/articles/360000920738-How-to-select-the-organization-to-use-in-the-CLI)
+For more information see the article [How to select the organization to use in the CLI](https://docs.snyk.io/snyk-cli/test-for-vulnerabilities/how-to-select-the-organization-to-use-in-the-cli)
 
 ### `--file=<FILE>`