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

This doesn't directly answer your question, but there's an <https://github.com/pulumi/pulumi/issues/4605|epic> to improve the stability of self-managed state backends slated for q4 on the <https://github.com/orgs/pulumi/projects/44|roadmap>

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

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

(I saw that epic last night :sweat_smile: )

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>

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.