API v2 Support

[wearhere]

Do you have plans to support Digital Ocean's v2 API? It seems impossible currently to authorize tugboat as it still requires API and client keys vs. v2's new personal access tokens.

[blom]

Support for version 2 is planned. In the meantime, keys for version 1 can be managed here:

https://cloud.digitalocean.com/api_access

[wearhere]

Oh thanks! I didn't see that you could still get to the v1 API page from the top of the v2 page.

[rickw]

In the v2 support are there plans for IPv6 support?

[petems]

Changed link in Authorize command to clarify: #108

[Vrtak-CZ]

vote 👍

[petems]

Requires 2.0 API, will be available in the future! 👍 See #122

[zlanich]

Any idea when API v2 will be implemented? DO completely disables API v1 when we invite team members because v1 doesn't support teams, so I can't invite any team members until then lol. Thanks.

[petems]

Hi @zlanich! You can see the progress here: #161

There's a beta release of the API 2.0 release version of the gem, you could give that a try in the mean time 👍

[zlanich]

I will do that very soon. Thanks!

Peter Souter wrote:

Hi @zlanich https://github.com/zlanich! You can see the progress
here: #161 #161

There's a beta release of the API 2.0 release version of the gem, you
could give that a try in the mean time 👍

—
Reply to this email directly or view it on GitHub
#102 (comment).

[mxdpeep]

API v1 will be shutdown on November 9th 2015

[steadystatic]

Just got the email from DigitalOcean and love Tugboat so I'm sweatin' this switchover in November. Anything that folks can do to help get Tugboat down with V2?

[petems]

Fixed by #183