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

Is this 4+ distributions in one pulumi program? I.e. one call to `up`

And is there any chance there's data dependencies between the distributions? Your not using outputs of one to set inputs of another?

Because if both of the above are the case I'd expect the engine to already issue these in parallel.

They're all being deployed in the same call to `up`, but they're created in a loop. Your instict makes me think to me that a call to `aws.cloudfront.get_distributions`  in the same loop may be causing it to block.

Going to shuffle that logic a bit.

Thanks for the hint!

I wouldn't expect get_distributions to block, except in Go because no tasks/promises there.

image.png

Destroying the stack definitely happens in parallel.

Thanks it's getting a bit late to go code digging here now, but I'll make a note to check this in the morning.

Woot! Seems that `get_distribution` _was_ blocking. I thought I was calling it such that it'd return an output object but I must have been calling it wrong.

This is working in parallel. Really appreciate your tip!

Good to hear, I'll see if I can work out _why_ its blocking because that's surprising to me and would be good to fix.

Makes total sense. I'm still novice at Pulumi, but let me know if there's anything I can do to assist.

Really loving it tho. Revolutionary product IMHO.

Looks like invokes in python are blocking, odd that they still return an awaitable. Something for us to improve in a future version.

Ah, alright. Really wish I was more familiar with the project's architecture so I could help improve it.

At least it seems we have a scent to track now!