Hi, I'm curious to know how people are handling running pulumi update in an HTTP API . Do you do a f...

millions-journalist-34868

01/24/2025, 8:57 PM

Hi, I'm curious to know how people are handling running pulumi update in an HTTP API . Do you do a fire and forget on the Up operation so calling it without waiting for the result?

modern-zebra-45309

01/24/2025, 9:03 PM

I've built an API that returned 202 ACCEPT together with a task ID that allowed the requester to query the status of the Pulumi call. That worked quite well.

many-country-10208

02/06/2025, 6:19 PM

@modern-zebra-45309 Are you managing the "task ID" yourself or are you returning the ID that Pulumi gives you when running an update?

modern-zebra-45309

02/06/2025, 6:23 PM

I generated a task ID myself and used it to name the job I launched so that I could find it later if a user queries for its state.

many-country-10208

02/06/2025, 6:34 PM

If you use Pulumi cloud, couldn’t you just use the ID you’re given to save that extra mapping? Or am I missing some additional benefit here?

modern-zebra-45309

02/06/2025, 6:41 PM

We did not use Pulumi Cloud but a self-hosted backend, so that wasn't an option. I didn't spend too much time thinking about which ID to use when I implemented it, I think I just generated a UUID and ran with it. Except when debugging, nobody ever saw this ID.

3 Views

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.