Given the current broken state of the non Pulumi backends wh

Question

Given the current broken state of the non Pulumi backends what is the best option for someone who is just getting started with Pulumi today <https github com pulumi pulumi issues 2522 issuecomment 966764817> I d like to begin doing deployments but I m afraid of committing to the GCP state store if the next release is going to invalidate it and force me to adopt all my created resources manually

freezing-van-87649 · Answer

This doesn t directly answer your question but there s an to improve the stability of self managed state backends slated for q4 on the

freezing-van-87649 · Answer

I ve been using S3 for a while without any major issues and I would be shocked if there wasn t a migration path after any updates but I ll see if any pulumi staff want to comment

able-camera-57198 · Answer

Yeah I ve kind of just come to be aware of the current state of things

able-camera-57198 · Answer

I saw that epic last night sweat smile

able-camera-57198 · Answer

I m hesitant to put it this way but I really feel like there might be some severe misdesigns in pulumi stack state stack configuration and the CLI behaviour <https github com pulumi pulumi issues 8402>

able-camera-57198 · Answer

My suspicion is that the way things ended up weren t explicitly designed but there might be a lot of implicit design that happened that s resulted in the CLI and stack configurations having some undesirable limitations