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

Have anyone implemented a rollback logic with Github actions or CircleCI for pulumi. If not, does exporting the stack json before a deploy and checking for any error to import the backup stack and  refresh with the exported stack a good approach?

That would rollback the stack, not the provider. So resources that Pulumi created would not be managed by Pulumi. That sounds like a worse situation to me.

You could do it automatically via `git revert`, which would put new commits that cause the code to return to its previous shape, then `up` that.

But I have never found that to be necessary. Generally, if you make a mistake, it gets caught in your first environment, you resolve it in a roll-forward manner, and it never goes any further.

Thats true, I currenlty have three env. Dev, Staging and Prod. I've been doing roll forward.

Thanks for the response. Based on your input, I should stay with the roll forward approach.