Sign in Dashboard Get started

Promote Pulumi stacks with CI/CD

Build a promotion pipeline that previews pull requests, deploys dev and staging on merge, and keeps production behind an explicit approval or deployment trigger.

Step 1 of 1

Choose platform

Choose an option to continue.

Frequently asked questions

Which stacks does this blueprint assume?
It assumes one Pulumi project with dev, staging, and production stacks. You can rename the stacks, but keep the promotion order and approval gate explicit.
Where do cloud credentials live?
The workflows and deployment settings are written for short-lived credentials from OIDC and Pulumi ESC. Do not store static cloud keys in the repository or workflow files.
Why is production different from staging?
Production changes need a deliberate human or policy-controlled release step. GitHub Actions uses a protected environment named production, while Pulumi Deployments leaves production as click-to-deploy or API-triggered because approval policy is organization-specific.
Can I adapt this to a monorepo?
Yes. Keep the Pulumi project under a stable directory such as infrastructure/, then use path filters so unrelated application changes do not trigger infrastructure deployments.
Does this create cloud resources?
The starter uses a tiny Pulumi program so the CI/CD shape is easy to test. Replace it with your real stack once the promotion flow works in your organization.