No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<@UB22XNXS8> I'm just gettign started with AWS CodePipeline/CodeBuild. CodePipeline seems to be really inflexible, but its advantage is staged pipelines where you can pause execution (for example, to do manual testing) before deploying to production. Does pulumi offer a way to do staged pipelines that I'm missing, just using codebuild? Or would CircleCI offer a better experirence?

Hi! Pulumi can fit into the workflow you describe, but doesn’t have a way to “pause and wait” during an update.

If you want a manual test step after updating staging, and then proceed to updating production, you would just need to create two different Pulumi stacks. (E.g. ‘pulumi update staging’ and then later ‘pulumi update production’.)

So either CI/CD system would support your use case, if I understand it correctly.

The CircleCI orbs launch just removes some boilerplate around writing your CI/CD script. But doesn’t materially change how Pulumi would be used to update cloud resources.

ok that makes sense - right at the beginning of setting this up so I'm not sure exactly where I'll end up. I want minimal repetition/cloned code and most CI systems don't seem to care about that.