I’m not a Pulumi team member but I guess I can answer one of your questions:

What is the operational impact of Pulumi being unavailable?

If you use Pulumi Service as your state backend, you won’t be able to perform any infrastructure changes until it’s back online (but it shouldn’t not affect already running things). One option to mitigate that is to store your state in other state backend (like S3 or GCS) but then you’re gonna miss some Pulumi specific features (https://www.pulumi.com/docs/intro/concepts/state/#backends). Another option is to use self-hosted version available in Pulumi Enterprise (https://www.pulumi.com/docs/guides/self-hosted/) and take all the responsibility on yourself.

Thanks @prehistoric-activity-61023

I’ve seen you already got some answers in a different channel but I hand’t seen that when I was writing this reply.

Yes, those are the important ones for our product.