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

Say I have 200 ec2 instances I want to roll from A to B.  Is there a way to limit the number in-flight ec2 instances that Pulumi will build/destroy at once?  (Rate limiting the pulumi API isn't an option due to the number of calls needed to support the app.)  Ideally what we want is for Pulumi to build 1, destroy 1, build 1, destroy 1 ... all night long.

are they in an autoscaling group? or have you defined 200x instances in a loop?

we basically have 200 shards &amp; we want to replace them one at a time

`pulumi up --parallel 1` will do it, but please test it first

also, hope you’re considering using an ASG :smile: