← All insightsCI/CD

Integrating Pulumi into your CI/CD pipeline

Nir Geier, CodeWizard · 30 November 2025 · 3 min read · Intermediate

Getting Pulumi into your pipeline is where it starts paying off - automated, repeatable and reviewed. Here is a working integration and the habits that keep it reliable.

A working pipeline snippet

Preview and deploy with the Pulumi GitHub Action.

yaml
- uses: pulumi/actions@v6
  with: { command: up, stack-name: acme/prod }
  env: { PULUMI_ACCESS_TOKEN: ${{ secrets.PULUMI_ACCESS_TOKEN }} }

Do this

  • Keep programs declarative; push logic into tested helpers
  • Use pulumi config set --secret for encrypted config
  • Write unit tests with the language's normal test tools

Avoid this

  • Putting imperative logic with side effects in resource code
  • Leaking secrets into stack config without encryption
  • No unit tests despite using a real language

Want senior help putting Pulumi to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult