Rewrite for Digital Ocean v2 API

[enzy]

DigitalOcean API Reference

Random notes:

• Ranges response handling

[barisusakli]

Looks like v2 is in open beta now. https://developers.digitalocean.com/v2/

[icodeforlove]

I decided to create a whole new api wrapper because this one lacks promise support, validation, and maintenance.

https://github.com/icodeforlove/doapi

For the most part i kept the method names the same for easy transition.

[digitaldesigndj]

+1 to @icodeforlove

Didn't run anything, but a quick glance was very promising! Thanks for sharing.

[icodeforlove]

BTW Digital Ocean says they will drop support for their v1 api in Nov, but this seems to be a lie. The following will break your v1 app.

• if you regenerate your v1 key it becomes a v2 key
• if you convert your account to a team account you lose v1 support

[andrewsomething]

@icodeforlove We will not be supporting new features for APIv1. When converting your account to a team, you are given a warning that you will no longer be able to use v1. The permissions structure for the team accounts is built around APIv2. In fact, allowing things like this are a big reason why we redesigned the API in the first place.

Non-team accounts can continue to use v1 and regenerate the key as often as needed. You can regenerate your APIv1 key here: https://cloud.digitalocean.com/generate_api_key