Skip to main content
Sign in Dashboard Get started
  1. Docs
  2. pulumi deployment get | CLI commands

pulumi deployment get | CLI commands

Generated for Pulumi CLI v3.242.0.

    [EXPERIMENTAL] Get details for a specific deployment

    Synopsis

    [EXPERIMENTAL] Get details for a specific deployment.

    The deployment may be referenced by its UUID or by its per-stack version number (the integer shown in the Pulumi Cloud UI, e.g. 9410 or #9410).

    Retrieves detailed information about a single Pulumi Deployments execution. The response includes the deployment’s current status, creation and modification timestamps, version number, the user who requested the deployment, the Pulumi operation type, the list of jobs (with their step-level status), and any stack updates produced by the deployment.

    pulumi deployment get <deployment-version> [flags]

    Options

      -h, --help            help for get
      --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")
      --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