pulumi policy compliance list | CLI commands

[EXPERIMENTAL] List compliance results grouped by entity

Synopsis

[EXPERIMENTAL] List compliance results grouped by entity.

Returns compliance results for policy issues grouped by stack, cloud account, or severity. Each row shows a compliance score (0-100%) per policy group/pack column.

Score values: 0-100 = compliance %, N/A = not applicable, ERR = configuration error.

pulumi policy compliance list [flags]

Examples

  # List compliance by stack (default)
  pulumi policy compliance list

  # List compliance by severity
  pulumi policy compliance list --group-by severity

  # List compliance by account as JSON
  pulumi policy compliance list --group-by account --output json

Options

      --count int         Maximum number of rows to display (default: all)
      --group-by string   How to group results: stack, account, or severity (default "stack")
  -h, --help              help for list
      --org string        The organization to fetch compliance results 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 compliance - [EXPERIMENTAL] Inspect policy compliance results