Cloudformation stack in unrecoverable state should be tainted

[hashibot]

This issue was originally opened by @torfredrik as hashicorp/terraform#5652. It was migrated here as part of the provider split. The original body of the issue is below.

---

If you create a stack that ends up in the state ROLLBACK_COMPLETE the only way to recover is to delete the stack and recreate it with a valid cloudformation template.

Using terraform I would expect the stack to be tainted when it reaches this state, and any updates I make to the template and apply to the stack should result in a recreation of the stack.

The problem is shown in this gist.

[mjalkio]

Is there a recommended workaround for this currently?

[wernerb]

This is still a problem for us. Is there a way to force delete?

[dan-petty]

I'm still dealing with this issue as well.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.