search

grisu / gricli

Grisu commandline client
7 stars 2 forks source link

"clean jobs" command, too dangerous, needs confirm? #185

Closed makkus closed 12 years ago

makkus commented 13 years ago

Just realized that the "clean jobs" command actually deletes all the users jobs. Before I assumed it would take a list of jobs to delete. Cleaning all of the users jobs can potentially be quite devastating if executed by accident, and I could see that happen sooner or later. Shouldn't we have some kind of "Are you really sure you want to do that?" confirmation question asked. If that can't be implemented, maybe user needs to execute clean jobs force or so, with the "force" part not being tab-completed?

If you think that is not an issue, just close this ticket...

sina-masoud-ansari commented 13 years ago

Yeah I would agree, there should be a check for clean job * as well, just to protect users as it is likely to happen. Are there any issues around implementing a 'Are you sure' type response that would favour a clean jobs force option?