pulumi stack policy list | CLI commands

[EXPERIMENTAL] List the Policy Groups and Policy Packs that apply to a stack

Synopsis

[EXPERIMENTAL] List the Policy Groups and Policy Packs that apply to a stack.

Lists the Policy Groups the stack is a member of and the Policy Packs those groups enable for it. Each pack is listed with the mode of the groups that enable it: preventative packs run during pulumi preview and pulumi up; audit packs report policy issues without blocking deployments.

Requires the Pulumi Cloud backend.

pulumi stack policy list [flags]

Examples

  # List the policies that apply to the current stack
  pulumi stack policy ls

  # List the policies that apply to another stack as JSON
  pulumi stack policy ls --stack acme/web/prod --output json

Options

  -h, --help            help for list
      --output string   Output format. Supported values are: default and json (default "default")
  -s, --stack string    The name of the stack to operate on. Defaults to the current stack

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 stack policy - [EXPERIMENTAL] Inspect the policies that apply to a stack