Ask for password when destroy a droplet
When destroy a droplet, system should ask to enter password to confirm before delete it for more safety. Since this is the most important decision.
Please add Termination protection for my droplets.
I dont want accidently deleting my main servers
Display the droplet name + info in the second screen/stage
I notice when I destroy servers an overlay comes up and covers the name of the server you are deleting. If you are moving quickly it would be easy to delete a server you do not want to delete. It seems like you should be able to lock a server or make it so a user can double and triple check. Amazon does a nice job of locking servers. Github does a nice job of double and triple checking when deleting a repo. Just an idea.
@Mathieu Martin: I agree! Something similar to GitHub would be nice, but now using the password. That might not be a good idea, especially for those having strong passwords.
Mathieu Martin commented
I completely agree with Luis: we need a feature like EC2's "termination protection" that can be enabled per machine.
Or maybe approach this like Github does when deleting a repo: confirm deletion by typing the repo name (in this case it would be the Droplet name).
Another similar option that I like would be having something similar to EC2 "termination protection". Just a attribute you can enable so the interface just doesn't allow you to destroy the server unless you disable that option again.
I think it is an urgent feature !!!!
Sebastiaan van Stijn commented
Seems like a sensible thing to do, especially since (as I understand) backups will be deleted as well when deleting a droplet, so if you did *not* manually create a snapshot, there's no way to restore your server/droplet
Yes that would be a nice security feature...
Jeffrey A. commented
I second this
Please make it
Would be a great option!
Agreed! I have never liked simple "are you sure you want to do this" questions. I have been conditioned over years to just automatically click that OK button. Asking for a password better communicates the seriousness of destroying a droplet along with all its data.
I would love a multi-step process or secondary password option for deleting a server. If someone gains access to your admin login it would be so simple for them to wipe out your active servers and backup images.
Bart Trojanowski commented
It would also be good to require an additional step to delete a server though the API.
We can fix this by displaying the droplet name in the modal during confirmation.