Scalable compute services.
Simple object storage.
Run managed Kubernetes clusters.
Tools & Integrations
Automate your infrastructure.
Deploy pre-built applications.
Connect, share and learn
DevOps and development guides
Questions & Answers
Development and systems Q&A
by Justin Ellingwood
Very important to have this especially in regards to killing droplets with the API.
It's time for DO to implement this; even Google Cloud has done it. So that some production workloads can be moved to DO.
This has just happened to me. Do users should be spared of such misery at the earliest
This has got to be "must have" if DO is to be a serious platform for enterprise deployments. We can use DO for dev but for production would have to stick with AWS until there is termination protection. With all the Infrastructure as Code, rapid build out and tear-down it is just too likely that at some point someone will kill a production node.
Maybe a quick win:
1. Give option for a Project (which would be for production) to disable API killing of resources. To kill them, must use UI.
2. In the UI - for all Projects - add a text box "are you really sure you want to kill the droplet" asking user to type in full name of the droplet. At least then you will have to think about the actual droplet you are killing.
You won't be notified about changes to this idea.