Actions
Feature #19637
openRecursive delete of workflow & associated intermediates
Start date:
Due date:
% Done:
0%
Estimated time:
Story points:
-
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.
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-11-09 sprint to 2022-11-23 sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-11-23 sprint to 2022-12-07 Sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-12-07 Sprint to 2022-12-21 Sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-12-21 Sprint to 2023-01-18 sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2023-01-18 sprint to 2023-02-01 sprint
Updated by Peter Amstutz almost 2 years ago
- Target version deleted (
2023-02-01 sprint) - Release set to 59
Updated by Peter Amstutz almost 2 years ago
- Target version set to To be scheduled
Updated by Brett Smith almost 2 years ago
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.
Updated by Peter Amstutz almost 2 years ago
- Target version changed from To be scheduled to To be groomed
- Story points deleted (
2.0)
Actions