pulumi policy issue list | CLI commands

[EXPERIMENTAL] List all policy issues for an organization

Synopsis

[EXPERIMENTAL] List all policy issues for an organization.

Returns a list of policy issues for the organization. Each issue represents a violation detected by a Policy Pack during a stack update or a continuous-compliance scan, and includes the violating resource, policy details, and enforcement level.

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

pulumi policy issue list [flags]

Options

      --all             Return all matching issues; mutually exclusive with --count
      --count int       Maximum number of issues to return (default 100)
  -h, --help            help for list
      --org string      The organization to list policy issues for
      --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