You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if a test samples workflow is manually cancelled, the steps to delete AWS/Azure resources are skipped. For example, here. It's crucial that we complete the cleanup step regardless of how the workflow terminates.
Delete Azure Resource Group only if Create Azure Resource Group step was successful.
Delete AWS Resources only if Deploy App step was successful.
Delete EKS Cluster only if Create EKS Cluster step was successful.
If a workflow is cancelled, do we want to make sure the resources are deleted, or do we want to exit the run right away? Because we also have Purge Resources workflow that runs every night to delete all the dangling resources.
What do we want to do when the workflow is cancelled? I'd be okay with both: stopping the run immediately (w/o deleting any resources) or stopping the run after deleting the resources.
Delete AWS Resources only if Deploy App step was successful.
This could be problematic for scenarios when the app deployment fails in partially deployed state, where some AWS resources for the app are deployed in which case we would still want to delete those AWS resources. Let me know if this scenario is not possible to happen.
Delete EKS Cluster only if Create EKS Cluster step was successful.
This sounds reasonable as long as failure of create EKS cluster guarantees cleanup of any underlying resources AWS created along the way.
If a workflow is cancelled, do we want to make sure the resources are deleted, or do we want to exit the run right away?
I think we should still run all the cleanup steps even if the workflow was cancelled. Purge resources workflow should ideally only be needed for cleanup of things out of control (RDS snapshots, for example). @willdavsmith thoughts?
Currently, if a test samples workflow is manually cancelled, the steps to delete AWS/Azure resources are skipped. For example, here. It's crucial that we complete the cleanup step regardless of how the workflow terminates.
AB#11442
The text was updated successfully, but these errors were encountered: