Infrastructure as Code
Pulumi manages infrastructure with general-purpose languages.
On this page
Use this page for fast recall. Use Full documentation when you want the complete end-to-end path.
A simple 5-step flow you can follow when using Pulumi in real work.
1) Setup
Install/run the tool and confirm version. Create a minimal config.
2) Small change
Do one small action end-to-end to prove the workflow.
3) Validate
Check output, logs, and status. Catch mistakes early.
4) Automate
Convert it into a repeatable script or pipeline step.
5) Productionize
Add safety: secrets, rollback, observability, and docs.
These are practical sequences you can copy into your own checklist or runbook.
Goal: Make infrastructure changes with a repeatable preview-first habit.
- Set config and secrets per stack.
- Run `pulumi preview` and review diffs.
- Run `pulumi up`.
- Verify outputs and cloud resources.
- Commit with notes and keep stacks isolated.
- Stacks
- Providers
- Components
Learning path (high-level):
- Stack setup
- Reusable components
- Policy controls
Create project
Command
pulumi newPreview changes
Command
pulumi previewDeploy
Command
pulumi upShort descriptions and practical intent. Search, filter, copy, and reuse.
Showing 13
pulumi versionShow Pulumi version.
pulumi newCreate a new project from template.
pulumi stack lsList available stacks.
pulumi stack init devCreate a new stack.
pulumi stack select devSwitch to a specific stack.
pulumi config set key valueSet stack configuration.
pulumi config set --secret password valueStore secrets securely.
pulumi previewPreview changes (like Terraform plan).
pulumi upDeploy changes.
pulumi refreshSync state with live resources.
pulumi stack outputShow stack outputs.
pulumi destroyDestroy all stack resources.
pulumi logs --followStream stack operation logs.
Small blocks you can drop into your terminal, config, or runbook.
Preview then deploy
bash
pulumi stack select dev
pulumi preview
pulumi upWhen things break, follow this order to stay calm and move fast.
- If preview differs unexpectedly: check config/stack selection and provider credentials.
- If secrets leak: use `pulumi config set --secret` and rotate credentials immediately.
The common mistakes that slow people down when using Pulumi.
- Copy-pasting commands without understanding inputs/outputs and side effects.
- Not documenting defaults (ports, paths, credentials) and then getting stuck in prod.
- Skipping logs and metrics when troubleshooting; always collect evidence first.
Do these tasks in order. You will feel the tool instead of just reading about it.
- Install or run the tool locally (or in Docker) and verify it works with a hello-world action.
- Create a minimal config and run the most common command 3 times (with a small change each time).
- Break something on purpose and document how you debugged it in your Notes.
Use these to test if you truly understand the basics (and can explain them clearly).
- Explain the tool’s role in a real CI/CD pipeline from commit to production.
- Describe the most common failure you’ve seen with this tool and how you fixed it.
- What would you monitor/alert on for this tool in production?