https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
👀 1
w
That's not expected; the behavior should match your expectation. The number of parallel resource creation operations is controlled with the 
--parallel
flag.
For my own curiousity, what CLI version are you using and what language?
m
Sorry Robbie, been off sick and didn't get back to you quickly. Currently using Python and Pulumi 
v3.66.0
with 
pulumi-aws
5.36.0
Without having looked too far into it, some of the team suspect that it might be related to how the python libraries communicate with the engine, and wait for resources to create. I unfortunately don't have code to point to at the moment though.
w
Hope you're feeling better! It's also possible that somewhere along the way the Python runtime added a blocking future to the code, which would also cause the outcome you're describing (I think). If your code is written such that the 20 resources are e.g. in a component resource, and the next 20 depend on that component, then you'd also get this same behavior.
m
I don't believe that in this case it'll be the component resources. I'll try and make a reproduction just with dynamic resources that sleep to eliminate any dependencies. I don't have a wealth of experience with asynchio let alone the deeper internals of the AWS Pulumi Python libraries - what could possibly cause some resources to be blocking futures and not others?
w
what could possibly cause some resources to be blocking futures and not others?
Programmer error on the Pulumi-side of things! Sorry if that was unclear. I'm saying it's possible it's a bug.
Open in Slack
PreviousNext
Powered by

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.

Powered by