pulumi policy issue get | CLI commands

[EXPERIMENTAL] Get the details of a specific policy issue

Synopsis

[EXPERIMENTAL] Get the details of a specific policy issue.

Returns the details of a single policy issue, including the violating resource, the Policy Pack and policy that flagged the violation, the enforcement level, severity, and the human-readable message produced by the policy.

Default output is a human-readable summary; pass –output=json for the full response as JSON.

pulumi policy issue get <issue-id> [flags]

Options

  -h, --help            help for get
      --org string      The organization that owns the issue
      --output string   Output format. Supported values are: default and json (default "default")

Options inherited from parent commands

      --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
  -C, --cwd string                   Run pulumi as if it had been started in another directory
      --disable-integrity-checking   Disable integrity checking of checkpoint files
  -e, --emoji                        Enable emojis in the output
  -Q, --fully-qualify-stack-names    Show fully-qualified stack names
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --memprofilerate int           Enable more precise (and expensive) memory allocation profiles by setting runtime.MemProfileRate
      --non-interactive              Disable interactive mode for all commands
      --otel-traces string           Export OpenTelemetry traces to the specified endpoint. Use file:// for local JSON files, grpc:// for remote collectors
      --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
      --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose

SEE ALSO

• pulumi policy issue - [EXPERIMENTAL] Inspect policy issues