json
nctl scan json
Scan Command
Scan JSON resources by validating them against custom policies.
nctl scan json [flags]
Scan Options
| Flag | Shorthand | Description |
|---|---|---|
--audit-as-warn |
Report violations from policies as warnings instead of failures | |
--file <string> |
mention the file name to store scan result | |
--debug |
Debug command | |
--insecure |
allow connection to an address with a self-signed or non-verifiable certificate (not recommended) | |
--help |
-h |
help for json command |
--publish |
Publish reports (default true) | |
--publish-token <string> |
scan reports publish token | |
--report-sourceid <string> |
Source ID used when publishing a report | |
--output <string> |
-o |
choose the output format of scan result. Available options are: json, text,yaml and sarif with the default option being text |
--policies <strings> |
-p |
specify path to policy files (local path, github URL, helm URL) to scan against custom policies |
--resources <strings> |
-r |
path to resource files (local path, github URL). scan specific resource files instead of all resources in a cluster, use this flag to point to a local path or gitHub URL containing the resource files |
--scan-report <string> |
-u |
Output scan report file (in JSON format) |
--token <string> |
Nirmata API Login Key (env NIRMATA_TOKEN) | |
--url <string> |
Nirmata server base URL (env NIRMATA_URL) |