Add support to cleanup task executions #3902
Comments
sabbyanandan
added
type/enhancement
|
This option would be a highly risky command to run in a higher-level environment like production. Especially, with the tasks as scheduled, and when you attempt to do this across all executions, things could get really bad, very fast. |
sabbyanandan
changed the title
|
We already support optionally also deleting task executions when destroying the task definition via #3903 — available since v2.6.1. |
|
@sabbyanandan Do we have a confirmation step for these deletes? I think if we did it, running a count query and presenting the user with how many task executions are about to be deleted would be a good compromise. Something like: |
|
Oh, that sounds like a great idea. I believe there's that option in Shell to be able to ask for user's confirmation. We could derive the count and build the experience around it. Thanks, @mminella! |
|
cc: @cppwfs @ilayaperumalg — let us know if you have any additional recommendations / concerns. |
|
I think this is a great addition for those folks in development and testing. IIIIII like it! |
sabbyanandan
modified the milestones:
Iteration 178 -> SCDF 2.7.0.M1,
Iteration 179 -> SCDF 2.7.0.RC1
sabbyanandan
modified the milestones:
Iteration 179 -> SCDF 2.7.0.M2,
Iteration 180 -> SCDF 2.7.0.GA
sabbyanandan
modified the milestones:
Iteration 180 -> SCDF 2.7.0.RC1,
Iteration 181 -> SCDF 2.7.0.GA
- This `all` option would remove all the task execution resources along with the task execution records - Allow option to remove only the `completed` task executions - Add controller endpoint to retrieve total task executions for performance reasons - Add new interface methods into TaskExecutionService to retrieve the task executions using the filter option - Add/update tests Resolves spring-cloud#3902
- This `all` option would remove all the task execution resources along with the task execution records - Allow option to remove only the `completed` task executions - Add controller endpoint to retrieve total task executions for performance reasons - Add new interface methods into TaskExecutionService to retrieve the task executions using the filter option - Add/update tests Resolves spring-cloud#3902 Fix deletion for composed task apps Add support for deletion by task name Add a separate REST endpoint /tasks/executions/info Move Tasks executions info to a separate controller
- This `all` option would remove all the task execution resources along with the task execution records - Allow option to remove only the `completed` task executions - Add controller endpoint to retrieve total task executions for performance reasons - Add new interface methods into TaskExecutionService to retrieve the task executions using the filter option - Add/update tests Resolves spring-cloud#3902 Fix deletion for composed task apps Add support for deletion by task name Add a separate REST endpoint /tasks/executions/info Move Tasks executions info to a separate controller
- This `all` option would remove all the task execution resources along with the task execution records - Allow option to remove only the `completed` task executions - Add controller endpoint to retrieve total task executions for performance reasons - Add new interface methods into TaskExecutionService to retrieve the task executions using the filter option - Add/update tests Resolves #3902 Fix deletion for composed task apps Add support for deletion by task name Add a separate REST endpoint /tasks/executions/info Move Tasks executions info to a separate controller
As a user, I'd like the ability to clean up all the task executions, so when I'm in an active dev mode on CF, I have the ability to clean slate the task footprint quickly.
Currently, we have the support to clean up the execution by a particular task execution ID.
It would be useful to expose the following option:
Acceptance:
--allwould clean up all the task executions that aren't actively running or in use by some other state in SCDF.The text was updated successfully, but these errors were encountered: