search

motdotla / digitalocean

The easiest and most complete rubygem for DigitalOcean.
http://rubygems.org/gems/digitalocean
MIT License
153 stars 42 forks source link

DISCUSSION: Digital Ocean V2 API #44

Closed motdotla closed 8 years ago

motdotla commented 10 years ago

Hey guys, particularly maintainers, as you've likely heard DO moved their V2 API out to beta. It's RESTful, more secure, and does pagination well.

Part of the magic of this repo was that it was heavily metaprogrammed. It allowed someone to easily add new endpoints with very little knowledge of the library.

In large part that was thanks to DO's V1 API - which I actually ended up loving despite not following generally accepted RESTful practices.

So, let's discuss moving this to V2. I think we'd all like to take a similar metaprogrammed approach if possible. Is it possible with the new V2 API?

jcblw commented 10 years ago

It is definitely possible all it is is changing up payload form, and methods. Should not be too hard to abstract those things.

rbishop commented 9 years ago

I noticed DigitalOcean created their own digitialocean/droplet_kit gem. Overall I still like this gem but one nice thing about theirs is that it is instance based instead of a singleton object.

As a design goal for the next major release could we consider having instances of a client object instead of having to set your client_id and api_key directly on the Digitalocean constant?

Thank you for all of your hard work on this!

motdotla commented 9 years ago

@rbishop I think you are correct here too. I generally agree.

motdotla commented 8 years ago

This has been almost a year since I cared for this. I'm opting to just leave it at V1 and point people to the official V2 gem.

https://github.com/digitalocean/droplet_kit

motdotla commented 8 years ago

https://github.com/motdotla/digitalocean/pull/51