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

pulumi deployment log | CLI commands

Generated for Pulumi CLI v3.242.0.

    [EXPERIMENTAL] Retrieve execution logs for a deployment

    Synopsis

    [EXPERIMENTAL] Retrieve execution logs for a 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).

    Returns log lines from a deployment. Pass –job and –step to scope to a specific step within a specific job; in step mode –count must be 1-499 (default 100 server-side). Pass –all to fetch every available log line, following the server’s pagination internally; –count and –all are mutually exclusive.

    Default output prints one log line per row; pass –output=json for a structured envelope.

    pulumi deployment log <deployment-version> [flags]

    Options

          --all             Fetch every available log line, following server-side pagination; mutually exclusive with --count
      --count int       The number of log lines to fetch, 1-499 in step mode (0 to leave unset)
  -h, --help            help for log
      --job int         The job index to fetch step-level logs for (-1 to leave unset) (default -1)
      --offset int      The offset within the step's logs (0 to leave unset)
      --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
      --step int        The step index within the job; requires --job (-1 to leave unset) (default -1)

    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