pulumi stack drift status | CLI commands

[EXPERIMENTAL] Show the current drift detection status for a stack

Synopsis

[EXPERIMENTAL] Show the current drift detection status for a stack.

Shows whether drift has been detected, the ID of the latest drift detection run, and whether a run is currently in progress.

pulumi stack drift status [flags]

Examples

  # Show drift status for the current stack
  pulumi stack drift status

  # Show drift status as JSON
  pulumi stack drift status --output json

  # Show drift status for a specific stack
  pulumi stack drift status --stack org/project/dev

Options

  -h, --help            help for status
      --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