Operations
Once your Pulumi program is written and first deployed, “operations” is everything that happens next: rolling out changes safely, running Pulumi from CI/CD, diagnosing failures, and recovering from incidents.
These pages cover the Day 2 workflows for running Pulumi at scale.
Sections
Stack management - Day-to-day stack operations: targeted updates, update plans, editing state files when recovery is needed, and configuring a self-managed (DIY) state backend.
Continuous delivery - Integrate Pulumi with your CI/CD platform of choice. Reference setups for Argo CD, GitHub Actions, GitLab CI/CD, Jenkins, and more.
Troubleshooting - Diagnose and recover from common failures including update conflicts, destroy failures, interrupted updates, and CI/CD pipeline issues.
Debugging - Attach a debugger, capture verbose logs, and trace performance for your Pulumi programs.
Least privilege security - Configure cloud provider credentials with the minimum permissions needed for safe infrastructure operations.
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.