By Tosoon
We use API to create Droplet from snapshot, most of time we get Droplets done in 10-20 mins, but sometimes it could take hours!!.
API v2 allows to retrieve Droplet status via action id, we can check the status say after 30mins, but if it is still ‘in-progress’, we don’t want to keep checking its status because we don’t know when it will be done. If this case, how can we stop the creation request so this “new” droplet will be auto-destroyed when it is done, or the creation process will be killed by DigitalOcean?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
There is not currently a method to stop a creation once it has been started. Those are fairly long create times you are seeing. Are you building large droplets from a snapshot image?
In a setup I built using the API with Ruby I have my initial process start a create and then spawn a second script which runs a loop checking the droplet status every 5 seconds until it returns “Active” and then updates my database. A similar method could be used which would allow you to set a flag in your database indicating a create is not needed so once the status = Active your script could proceed to delete the droplet if you have set this flag.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.