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

Hmm I’m not too sure where to ask this… but I have a stack that deploys an app to ECS/Fargate… the stack has 3 `awsx.ecs.FargateService`s. When we want to release new code, we push a new docker image to our ECR and run pulumi up with the new image in the task definition. I’m finding, however, that pulumi up runs and updates the 3 resources in sequence rather than in parallel. Is there a way to get them to run in parallel? My command is just `pulumi up -y …`

Is there any chance it was related to these:

<https://github.com/pulumi/pulumi-awsx/pull/1334>
<https://github.com/pulumi/pulumi/issues/7629>

ohhh <https://github.com/pulumi/pulumi-awsx/issues/1250#issuecomment-2203388165>

`poetry update` =&gt; `Updating pulumi-awsx (2.12.1 -&gt; 2.15.0)` :pray::skin-tone-4: