Backlog #410

ask for confirmation on delete operation

Added by olivier sallou about 10 years ago. Updated almost 7 years ago.

Status:PendingStart date:11/15/2010
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:CLI
Target version:-

Description

Hi,
I think that delete/destroy operation such as "onevm delete" should request confirmation before doing so to avoid mistakes and unwanted deletion.
For possible wrappers above those scripts, an option could avoid asking so (such as onvm -force delete ..)

request_410.patch Magnifier (6.58 KB) olivier sallou, 11/19/2010 03:25 PM

Associated revisions

Revision d87a18b7
Added by Abel Coronado over 3 years ago

B #4978 Solved bug in date sorting 'Registration Time' (#410)

Revision a0cc0632
Added by Abel Coronado over 3 years ago

B #4978 Solved bug in date sorting 'Registration Time' (#410)

Revision 00cb3098
Added by Abel Coronado over 3 years ago

B #4978 Solved bug in date sorting 'Registration Time' (#410)

(cherry picked from commit d87a18b71cfc2cae0419ad7005178f140e18aab9)

History

#1 Updated by olivier sallou about 10 years ago

I join a git patch on oneuser, oneimage,onehost,oneimage and onevnet scripts to add a confirmation prompt on delete operations.
If delete is done with additional force option, no prompt is requested to the user.
Example
onevm delete 1
Are you sure... [Y/n]?

If not Y, process exits.

onevm delete force 1
...
deleted!

#2 Updated by Ruben S. Montero over 7 years ago

  • Tracker changed from Request to Feature
  • Category set to CLI

This is in sunstone we can add that for the cli two

#3 Updated by Ruben S. Montero over 7 years ago

  • Priority changed from Normal to Low

#4 Updated by Ruben S. Montero over 7 years ago

  • Tracker changed from Feature to Backlog

#5 Updated by Ruben S. Montero over 7 years ago

  • Status changed from New to Pending

#6 Updated by Ruben S. Montero almost 7 years ago

  • Priority changed from Low to Normal

Also available in: Atom PDF