pulumi stack drift list | CLI commands

[EXPERIMENTAL] List drift detection runs for a stack

Synopsis

[EXPERIMENTAL] List drift detection runs for a stack.

Returns drift detection runs for the specified stack. Each run includes whether drift was detected, the run status, and details about detection and remediation phases.

By default, the first 10 results are shown. Use –count to request more, or –all to fetch every run.

pulumi stack drift list [flags]

Examples

  # List drift runs for the current stack
  pulumi stack drift list

  # Show the last 50 drift runs
  pulumi stack drift list --count 50

  # Fetch all drift runs as JSON
  pulumi stack drift list --all --output json

Options

      --all             Fetch all results (mutually exclusive with --count)
      --count int       Number of results to display (fetches multiple pages if needed)
  -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:// 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 drift - [EXPERIMENTAL] Inspect stack drift detection results