Add ability to protect (or ignore) certain droplets so they can't be demolished inadvertently

[geeknik]

What is the problem this feature would solve? Please describe. Sometimes when I'm using doctl, I manage to delete the wrong droplet.

Describe the solution you'd like I'd like to know if it would be possible to add a way to ignore certain droplets so doctl can't demolish them inadvertently.

Additional context It could be added to the existing $HOME/.config/doctl/config.yaml or a new file called $HOME/.config/doctl/protect.yaml

Example:

protect:
  droplets: "293857,1230985720643,1031689246,283756198,9237859183,9128375135"

[scotchneat]

Hi @geeknik, thank you for your request!

We've received similar requests like this for doctl, as well as the API and the cloud UI. While I think it is possible to implement something within doctl, the feature would be limited to the tool. Since this feature would be beneficial across the other interfaces, I've reached out to respective teams to include this request in the ongoing conversation.