Stack management
These pages cover the day-to-day operations of running Pulumi stacks: scoping updates to specific resources, previewing changes before they apply, safely editing state when recovery is needed, and configuring a self-managed state backend.
Pages
Targeted updates - Limit which resources Pulumi operates on with --target, --exclude, and --target-replace. Learn the trade-offs of partial operations and when to use them.
Update plans - Preview and review infrastructure changes before applying them. Update plans help you catch unintended modifications and coordinate changes across teams.
Editing state files - Safe techniques for modifying Pulumi state when normal operations can’t recover. Use sparingly and always back up state first.
Using a DIY backend - Configure a self-managed state backend with AWS S3, Azure Blob Storage, Google Cloud Storage, PostgreSQL, or the local filesystem.
Thank you for your feedback!
If you have a question about how to use Pulumi, reach out in Community Slack.
Open an issue on GitHub to report a problem or suggest an improvement.