Security reviewing Pulumi SaaS, and one question came up re: DRP (disaster recovery planning) strategy if/when Pulumi SaaS goes down. I was thinking of saving the intermediary yaml files somewhere, so we can still deploy our stuff when the Pulumi SaaS becomes unavailable (down for maintenance or looses network connectivity) Using a GCP or Azure bucket for state management can help too, but doesn't cover the network connectivity scenario Anyone here has put a DRP strategy in place?

the Pulumi SaaS itself has backup/DR plans, contact support@pulumi.com for more information about that as for your own plan: you could export the state file after every operation, but you lose a lot of the benefits of our console: it largely depends on your risk tolerance

Hi @straight-cartoon-24485, Liz from the Pulumi team here 👋 like @billowy-army-68599 mentioned above, Pulumi SaaS has backup/DR plans. We’re happy to chat through this in more detail if you’d like? Just send me a DM and we’ll arrange a time to connect.