pulumi policy exception list | CLI commands

[EXPERIMENTAL] List policy exceptions for an organization

Synopsis

[EXPERIMENTAL] List policy exceptions for an organization.

Lists the organization’s active policy exceptions, most recently created first. Pass a Policy Pack name to list only that Policy Pack’s exceptions.

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

pulumi policy exception list [policy-pack] [flags]

Examples

  pulumi policy exception list
  pulumi policy exception list aws-security --stack web/prod
  pulumi policy exception list --status active --status removed --output json

Options

  -h, --help                 help for list
      --org string           The organization to list policy exceptions for
      --output string        Output format. Supported values are: default and json (default "default")
      --policy string        Only list exceptions that name this policy
      --stack string         Only list exceptions with targets in this stack, as <project>/<stack>
      --status stringArray   Only list exceptions with this status: active (default) or removed; may be repeated

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:// or https:// 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 exception - [EXPERIMENTAL] Manage policy exceptions