This message was deleted.

sparse-intern-71089

02/27/2019, 5:35 PM

This message was deleted.

incalculable-sundown-82514

02/27/2019, 5:39 PM

It might be a bit esoteric but you can think of Pulumi as a “graph executor” - it receives a graph of your desired state, turns that graph into a set of concrete steps that need to be completed, and then executes them all in order, possibly in parallel. Since Pulumi lets you inspect the outputs of resources that are getting created as part of this graph execution, it’s naturally the case that the ouptuts of a resources resolve asynchronously, as resources get created and Pulumi advances the execution of the graph. The asynchrony mirrors data flow dependencies between resources, and really when you’re writing a Pulumi program what you’re doing is connecting together different asynchronous streams of data. It’s confusing when these things don’t happen synchronously, but doing things asynchronously lets us present a facade of an imperative object model on top of a declarative, asynchronous data model.

incalculable-sundown-82514

02/27/2019, 5:39 PM

People do run into this often, and it’s unfortunate that this leaks into user programs the way that it does. We thought hard about this and weren’t able to come up with anything better that still had the properties that we wanted

thousands-notebook-91098

02/27/2019, 5:40 PM

thank you for the explanation, that was very well presented

thousands-notebook-91098

02/27/2019, 5:40 PM

you're just making me want to find more reasons to give pulumi a whirl at work

incalculable-sundown-82514

02/27/2019, 5:40 PM

yay! 😄

incalculable-sundown-82514

02/27/2019, 5:41 PM

I think the only time you really only ever need to think about asynchrony with Pulumi programs is when you interact with data sources - I think we do a pretty OK job hiding it everywhere else.

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.