Feature #19637
open
Recursive delete of workflow & associated intermediates
Added by Peter Amstutz about 2 years ago.
Updated almost 2 years ago.
Description
It might make sense to implement this as an API-side feature -- when deleting a container request, have an option that deletes the associated output collection, log collection, and all the sub-requests. Then the client side just has to include the "delete recursive" parameter.
- Target version changed from 2022-11-09 sprint to 2022-11-23 sprint
- Description updated (diff)
- Description updated (diff)
- Target version changed from 2022-11-23 sprint to 2022-12-07 Sprint
- Target version changed from 2022-12-07 Sprint to 2022-12-21 Sprint
- Target version changed from 2022-12-21 Sprint to 2023-01-18 sprint
- Target version changed from 2023-01-18 sprint to 2023-02-01 sprint
- Target version deleted (
2023-02-01 sprint)
- Release set to 59
- Target version set to To be scheduled
I think before we put this on a sprint, we should decide whether we're going to implement this in the API server, or strictly client-side. Right now the ticket is wishy-washy about that.
- Target version changed from To be scheduled to To be groomed
- Story points deleted (
2.0)
Also available in: Atom
PDF
Updated by 
Updated by