pulumi-cli

What problem does it solve?

Pulumi CLI operations can leave stacks in inconsistent or stuck states, and managing state changes, migrations, and non-interactive CI deployments is error prone. This guide focuses on operational tasks—recovering interrupted updates, repairing corrupt state, moving resources between stacks, and safely importing or exporting state—so you can restore stability without unintended resource recreation or data loss.

Core Features & Use Cases

• Clear pending or stuck operations and resume deployments using refresh, cancel, and state repair patterns.
• Move, rename, import, or delete resources from state to avoid destructive cloud operations while preserving live resources.
• Backup and restore state, migrate backends, and perform atomic state moves between stacks for refactoring or environment changes.
• CI/CD automation guidance: required environment variables, non-interactive flags, and safe pipeline steps for preview and deploy.
• Protect critical resources and enforce safe workflows with state protection, previews, and best-practice backups.

Quick Start

Recover a stack stuck with pending operations by running a refresh with clear pending creates, canceling the running update if necessary, exporting a backup of the current state, and then applying state repair or import as appropriate.