-
Notifications
You must be signed in to change notification settings - Fork 33
Description
Description
If you encountered an error during aio app undeploy, for example if an action does not exist (it may have been manually deleted), it errors out and does not continue undeploying the rest.
There is no point in stopping undeploy since there is no rollback.
If we have to undeploy A, B, C, D, E and it errors during C -- A and B have already been undeployed, and D, and E are left undeployed.
Proposed fix
If an error occurs during undeploy, we continue with the rest of the undeployment, and just log the error - but the return code should be 0 (success).
Only this specific type of error will allow the command to continue (and be successful) any other type of error, it will be thrown.
Workaround
Deleting everything in the package may help:
aio rt package delete YOUR_PACKAGE_NAME_HERE --recursive