Please describe what you would like to see in this project
Currently if a workflow fails to complete because of an error condition, the artifacts already created (containers or other kubernetes objects) are left in their most recent state and require manual cleanup. The engine should instead capture the failure state and delete the stale artifacts.
Please describe your use case
Particularly when developing new workflows and plugins and running frequent deployment tests, the stale artifacts can build up quickly and can create conflicts. But even in more "production" use cases, I don't think we want to leave these things lingering on the system.
Additional context
I think cleanup should be the default behavior, but I suspect there are reasons we may want to have the option to override the behavior and leave the stale artifacts in place.
Please describe what you would like to see in this project
Currently if a workflow fails to complete because of an error condition, the artifacts already created (containers or other kubernetes objects) are left in their most recent state and require manual cleanup. The engine should instead capture the failure state and delete the stale artifacts.
Please describe your use case
Particularly when developing new workflows and plugins and running frequent deployment tests, the stale artifacts can build up quickly and can create conflicts. But even in more "production" use cases, I don't think we want to leave these things lingering on the system.
Additional context
I think cleanup should be the default behavior, but I suspect there are reasons we may want to have the option to override the behavior and leave the stale artifacts in place.