pulumi env change-request | CLI commands

[EXPERIMENTAL] Manage change requests

Synopsis

[EXPERIMENTAL] Manage change requests

When an environment is protected by approval rules, changes to it go through a change request that must be approved before it is applied. Change requests are created by commands that accept –draft, such as env edit and env set. Use env open --draft=<id> to open the draft version of an environment.

Subcommands exist for listing, viewing, diffing, approving, applying, closing, commenting on, rebasing, and showing the events of change requests.

pulumi env change-request [flags]

Examples

  # Propose a change, then review and apply it
  pulumi env set my-project/prod app.replicas 3 --draft
  pulumi env change-request list --env my-project/prod
  pulumi env change-request get <change-request-id>
  pulumi env change-request approve <change-request-id> -m "Looks good"
  pulumi env change-request apply <change-request-id>

Options

  -h, --help                  help for change-request
  -o, --organization string   the organization that owns the change request (defaults to your default organization)

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
      --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 - Manage environments
• pulumi env change-request apply - [EXPERIMENTAL] Apply a change request.
• pulumi env change-request approve - [EXPERIMENTAL] Approve a change request.
• pulumi env change-request close - [EXPERIMENTAL] Close a change request.
• pulumi env change-request comment - [EXPERIMENTAL] Comment on a change request.
• pulumi env change-request diff - [EXPERIMENTAL] Show the change a change request proposes.
• pulumi env change-request get - [EXPERIMENTAL] Show a change request.
• pulumi env change-request list - [EXPERIMENTAL] List change requests.
• pulumi env change-request log - [EXPERIMENTAL] Show a change request’s events.
• pulumi env change-request rebase - [EXPERIMENTAL] Rebase a draft onto the environment’s current revision.
• pulumi env change-request unapprove - [EXPERIMENTAL] Remove your approval from a change request.