ec opa inspect
Inspect OPA bundle(s) or Rego files.
Synopsis
Inspect OPA bundle(s) or Rego files.
The 'inspect' command provides a summary of the contents in OPA bundle(s) or a single Rego file. Bundles are gzipped tarballs containing policies and data. The 'inspect' command reads bundle(s) and lists the following:
-
packages that are contributed by .rego files
-
data locations defined by the data.json and data.yaml files
-
manifest data
-
signature data
-
information about the Wasm module files
-
package- and rule annotations
Example:
$ ls bundle.tar.gz $ opa inspect bundle.tar.gz
You can provide exactly one OPA bundle, path to a bundle directory, or direct path to a Rego file to the 'inspect' command on the command-line. If you provide a path referring to a directory, the 'inspect' command will load that path as a bundle and summarize its structure and contents. If you provide a path referring to a Rego file, the 'inspect' command will load that file and summarize its structure and contents.
ec opa inspect <path> [<path> [...]] [flags]
Options
- -a, --annotations
-
list annotations (Default: false)
- -f, --format
-
set output format (Default: pretty)
- -h, --help
-
help for inspect (Default: false)
- --v1-compatible
-
opt-in to OPA features and behaviors that are enabled by default in OPA v1.0 (Default: false)
Options inherited from parent commands
- --debug
-
same as verbose but also show function names and line numbers (Default: false)
- --kubeconfig
-
path to the Kubernetes config file to use
- --logfile
-
file to write the logging output. If not specified logging output will be written to stderr
- --quiet
-
less verbose output (Default: false)
- --timeout
-
max overall execution duration (Default: 5m0s)
- --trace
-
enable trace logging, set one or more comma separated values: none,all,perf,cpu,mem,opa,log (Default: none)
- --verbose
-
more verbose output (Default: false)