based on your inputs, i tried to frame the following state flow:
export -> will set stack to (EXPORT, [COMPLETED|FAILED])
abandon -> ONLY on (EXPORT, COMPLETED) allow abandon set to (ABANDON, [COMPLETED|FAILED])
delete -> on (ABANDON, FAILED), (EXPORT, [COMPLETED|FAILED]) don't allow to delete, otherwise, like current behavior
delete (with force_delete parameter) -> even on on (ABANDON, FAILED) allow to force delete
Here, the last option force_delete helps to delete the stack, in case user need to delete forcefully.
zaneb, thanks for pointing out the diff.
based on your inputs, i tried to frame the following state flow:
export -> will set stack to (EXPORT, [COMPLETED|FAILED])
set to (ABANDON, [COMPLETED|FAILED])
abandon -> ONLY on (EXPORT, COMPLETED) allow abandon
delete -> on (ABANDON, FAILED), (EXPORT, [COMPLETED|FAILED]) don't allow to delete, otherwise, like current behavior
delete (with force_delete parameter) -> even on on (ABANDON, FAILED) allow to force delete
Here, the last option force_delete helps to delete the stack, in case user need to delete forcefully.
kindly provide your feedback. Thanks.