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

got an example use case?
think you might be interested in the <https://www.pulumi.com/docs/guides/automation-api/|automation api> (also <#C019YSXN04B|>)

You want automation-api or separate projects chained together in a script. Individual Pulumi projects are declarative, which means synchronicity is impossible. You're not calling the API when you do something like `new aws.ec2.Instance()`. You're just building a desired state, that Pulumi brings into existence later (after it has finished building that desired state).

Yeh with engine changes or some hackery this would be possible, but I can't see why you would want to do so.