pulumi deployment list | CLI commands

[EXPERIMENTAL] List deployments for a stack

Synopsis

[EXPERIMENTAL] List deployments for a stack.

Returns deployments for the selected stack, showing each deployment’s ID, operation, status, version, initiator, and the time it was last modified. Default output is a human-readable table; pass –output=json for a JSON envelope.

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

pulumi deployment list [flags]

Examples

  # List the most recent deployments for the current stack.
  pulumi deployment list

  # List the last 50 deployments.
  pulumi deployment list --count 50

  # Fetch every deployment as JSON.
  pulumi deployment list --all --output json

  # Sort ascending by a server-supported field.
  pulumi deployment list --sort created --asc

Options

      --all             Fetch all results (mutually exclusive with --count)
      --asc             Sort in ascending order (default descending)
      --count int       Number of results to display (fetches multiple pages if needed)
  -h, --help            help for list
      --output string   Output format. One of: default, json (default "default")
      --sort string     The field to sort results by
  -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")
      --config-file string           Override the file name where the deployment settings are specified. Default is Pulumi.[stack].deploy.yaml
  -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 deployment - [EXPERIMENTAL] Manage stack deployments on Pulumi Cloud