If the stack exists but is in a "rollbacked" state, cumulus considers it built

[gergnz]

When doing a creating but a sub-stack exists in CF, cumulus considers it OK, and doesn't create, thus any other stacks that depend on it, fail.

[peterkh]

This is a tricky one. I get what your asking for and hit this all the time myself. The issue I see is that it feels dangerous to me to automatically delete it. Could look at adding a prompt if this situation is encountered. "Stack xxx exists, but in rollbacked state, delete?"

[gergnz]

👍 Sounds good. Maybe also add a flag e.g --force "delete rollbacked stacks and recreate them. Use wisely" or something like that, to avoid the prompt if using in automation.

[prologic]

(y)