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

So, am I guessing right that you want to build a API which triggers `stack.up()` and returns HTTP response before `stack.up()` is ready?

yep correct. i was hoping there’s a way to expose an underlying coroutine to use with asyncio.create_task (or a separate api for async usage, or something)

<https://github.com/pulumi/pulumi/issues/8176>

But I think you could possibly do this by wrapping the calls in a coroutine yourself

wouldn’t they block the entire event loop?

yeah possibly, tbh never tried this myself i dunno if what i'm suggesting is realistic

AIUI (i’ve got some asyncio experience, but i’m not an expert) there has to be something that’s Awaitable for it to avoid blocking the event loop

it may potentially be not-absurd to wrap it in multiprocessing first

oh neat, i see it’s ultimately just wrapping subprocess, that means it should be fairly straightforward to make an asyncio version …

Yeah just keep in mind this caveat: <https://github.com/pulumi/pulumi/issues/6052>
But as long as they're in different processes you're golden.