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

pulumi deployment cancel | CLI commands

Generated for Pulumi CLI v3.242.0.

    [EXPERIMENTAL] Cancel an in-progress deployment

    Synopsis

    [EXPERIMENTAL] Cancel an in-progress deployment.

    Terminates an in-progress Pulumi Deployments execution. If the deployment is currently running, it is stopped immediately. If the deployment is queued but has not yet started, it is removed from the queue.

    Canceling a deployment is a dangerous action and may leave the stack in an inconsistent state if canceled during the execution of a Pulumi operation.

    pulumi deployment cancel <deployment-id> [flags]

    Examples

      # Cancel a deployment of the current stack.
  pulumi deployment cancel dep-abc123

  # Cancel a deployment of a different stack.
  pulumi deployment cancel dep-abc123 --stack acme/web/prod

  # Skip the confirmation prompt.
  pulumi deployment cancel dep-abc123 --yes

  # Emit JSON for scripting.
  pulumi deployment cancel dep-abc123 --yes --output json

    Options

      -h, --help            help for cancel
      --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
  -y, --yes             Skip confirmation prompts, and proceed with cancellation anyway

    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