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

Pulumi drives towards a desired state, so there's no automatic rollback per-se. can you elaborate a little more on what you're trying to achieve?

another important thing is that I'm using my a local backend (pulumi login --local). So, let's say that I have a program deploying A, B and C. If the program succeeds deploying A but for some reason it fails when running B, my deployed stack will be in an inconsistent state, so at this point I would like to be able to rollback to last successfully deployed stack, leaving the deployed solution in a consistent state

Pulumi drives towards the state of your code is how pulumi works, when you say "roll back to last successfully deployed stack" - what do you mean? you'd have to set your code to the state it would be in