pulumi-cancel

Cancel a stack's currently running update, if any

$ pulumi cancel [stack_name]

$ pulumi cancel --yes

$ pulumi cancel --help

pulumi cancel [--stack ] [--yes]

--stack
    The name of the stack to cancel. Defaults to the current stack.

--yes
    Skip confirmation prompts and proceed with cancellation.

The `pulumi cancel` command gracefully terminates a Pulumi update that is currently in progress. This is useful when an update is taking too long, is stuck, or is making changes that are unexpected. Cancelling an update attempts to roll back the changes made so far, though the completeness of the rollback depends on the provider and resource types involved. The command does not delete any deployed resources, but rather stops the current deployment process.
It's important to understand that cancelling an update might leave your infrastructure in an inconsistent state. Always review the state after a cancel to ensure the infrastructure is in the desired state.

Cancelling an update can leave your infrastructure in an inconsistent state. Ensure to review the state of your stack after the command.

The effectiveness of the rollback process after a `pulumi cancel` depends on the resource providers used and their ability to revert changes made. Some resources may roll back cleanly, while others may require manual intervention.
Some resources cannot be reverted.

By default, `pulumi cancel` prompts for confirmation before proceeding. Using the `--yes` flag skips this confirmation, which is helpful for automation.

The `pulumi cancel` command was introduced as part of the Pulumi CLI to provide a mechanism for interrupting and reversing updates. Its usage is primarily for situations where updates are failing or taking an unexpectedly long time. The feature has evolved along with the Pulumi platform, with improvements to its reliability and the quality of rollback behavior.

pulumi up(1), pulumi destroy(1), pulumi stack(1)