---
title: pulumi env change-request approve | CLI commands
url: /docs/iac/cli/commands/pulumi_env_change-request_approve/
---



[EXPERIMENTAL] Approve a change request.

## Synopsis

[EXPERIMENTAL] Approve a change request

This command shows the change that the change request proposes and asks for confirmation,
then approves its latest revision. Use `env change-request get` to see how many approvals
are still required.

```
pulumi env change-request approve <change-request-id> [flags]
```

## Examples

```
  # Approve a change request
  pulumi env change-request approve <change-request-id>

  # Approve with a comment
  pulumi env change-request approve <change-request-id> -m "Looks good"

  # Show the proposed change without approving it
  pulumi env change-request approve <change-request-id> --dry-run
```

## Options

```
      --dry-run          show the proposed change without approving it
  -h, --help             help for approve
  -m, --message string   a comment to add with the approval
  -y, --yes              skip the confirmation prompt
```

## 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](/docs/iac/cli/commands/pulumi_env_change-request/)	 - [EXPERIMENTAL] Manage change requests