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

Would that be equivalent to `pulumi up --parallel 1`?

Obviously doesn't change the order in which resources are processed, but maybe it's close enough for you needs?

The only other thing I'm aware of would be to use `--target-dependents --target &lt;one host&gt;`, then repeat for each host... :disappointed:

An alternative could be to chain the hosts together via `dependsOn` so that one depends on the previous one

<@U012UJTT55M> yea I think the explicit targeting might be what I need to do :disappointed:. I tried the parallel=1 already and it walked from the leaf dependencies down level wise (e.g. detached volumes and then reprovisioned hosts).

<@UTH0AMTQQ> hrm chaining could be interesting…

i’ll give it a try the AttachVolume(s) and instance creation are encapsulated in a ComponentResource so might just work!