[X] I have searched existing issues, it hasn't been reported yet
Use case description
I would like to be able to continue app removal process even after removal failed somewhere between stacks. For example sessions expired and half the app was not removed.
Currently if during removal service (stack) is not found, whole app removal is stopped because of Serverless throws an exception
Stack '<your-stack>' does not exist
Proposed solution (optional)
Handle missing stack exception and skip that stack and continue removal process as usual or skip missing stack before even starting removal process.
Is there an existing issue for this?
Use case description
I would like to be able to continue app removal process even after removal failed somewhere between stacks. For example sessions expired and half the app was not removed.
Currently if during removal service (stack) is not found, whole app removal is stopped because of Serverless throws an exception
Stack '<your-stack>' does not existProposed solution (optional)
Handle missing stack exception and skip that stack and continue removal process as usual or skip missing stack before even starting removal process.