pulumi env change-request log | CLI commands

[EXPERIMENTAL] Show a change request’s events.

Synopsis

[EXPERIMENTAL] Show a change request’s events

This command shows a change request’s events, such as new revisions, approvals, comments, and status changes.

pulumi env change-request log <change-request-id> [flags]

Examples

  # Show a change request's events
  pulumi env change-request log <change-request-id>

  # Show a change request's events as JSON
  pulumi env change-request log <change-request-id> --output json

Options

  -h, --help            help for log
      --output string   output format: "text" (default) or "json" (default "text")

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
      --env string                   The name of the environment to operate on.
  -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
  -o, --organization string          the organization that owns the change request (defaults to your default organization)
      --otel-traces string           Export OpenTelemetry traces to the specified endpoint. Use file:// for local JSON files, grpc:// or https:// 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 env change-request - [EXPERIMENTAL] Manage change requests