This message was deleted.

sparse-intern-71089

10/29/2020, 8:28 PM

This message was deleted.

little-cartoon-10569

10/29/2020, 8:29 PM

Would that be equivalent to

pulumi up --parallel 1

little-cartoon-10569

10/29/2020, 8:30 PM

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

little-cartoon-10569

10/29/2020, 8:31 PM

The only other thing I'm aware of would be to use

--target-dependents --target <one host>

, then repeat for each host... 😞

faint-table-42725

10/29/2020, 9:27 PM

An alternative could be to chain the hosts together via

dependsOn

so that one depends on the previous one

brief-printer-34348

10/30/2020, 8:18 PM

@little-cartoon-10569 yea I think the explicit targeting might be what I need to do 😞. I tried the parallel=1 already and it walked from the leaf dependencies down level wise (e.g. detached volumes and then reprovisioned hosts).

brief-printer-34348

10/30/2020, 8:18 PM

@faint-table-42725 hrm chaining could be interesting…

brief-printer-34348

10/30/2020, 8:19 PM

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

👍 1

Open in Slack

Previous Next

Pulumi Community

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.