---
title: Operations
url: /docs/iac/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](/docs/iac/operations/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](/docs/iac/operations/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](/docs/iac/operations/troubleshooting/)** - Diagnose and recover from common failures including update conflicts, destroy failures, interrupted updates, and CI/CD pipeline issues.

**[Debugging](/docs/iac/operations/debugging/)** - Attach a debugger, capture verbose logs, and trace performance for your Pulumi programs.

**[Least privilege security](/docs/iac/operations/iac-least-privileges/)** - Configure cloud provider credentials with the minimum permissions needed for safe infrastructure operations.