pulumi stack history events | CLI commands

[EXPERIMENTAL] Retrieve engine events for an update

Synopsis

[EXPERIMENTAL] Retrieve engine events for a specific update of a stack.

Engine events represent individual resource operations and diagnostic messages produced during an update. By default a single page of events is returned.

This command requires the Pulumi Cloud backend.

pulumi stack history events <update-id> [flags]

Examples

  # Show the first page of events in a human-readable table.
  pulumi stack history events <update-id>

  # Return at least 500 events.
  pulumi stack history events <update-id> --count 500

  # Return every event for the update.
  pulumi stack history events <update-id> --all

  # Emit the raw event stream as JSON for scripting.
  pulumi stack history events <update-id> --all --output json

  # Filter to a specific resource URN.
  pulumi stack history events <update-id> \
      --urn urn:pulumi:dev::proj::aws:s3/bucket:Bucket::my-bucket

Options

      --all                      Return every event for the update
      --count int                Return at least this many events, fetching additional pages as needed
      --event-type stringArray   Filter by Pulumi Cloud engine event type code; numeric, repeatable
  -h, --help                     help for events
      --include-non-activated    Include events not yet marked as activated
      --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
      --urn string               Filter by resource URN

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 history - Display history for a stack