[
https://issues.apache.org/jira/browse/JCLOUDS-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604465#comment-14604465
]
Chris Custine commented on JCLOUDS-613:
---------------------------------------
[~nacx] I rebased on master and merged a few pom.xml and generic conflicts from
our branches. Resulting branch submitted as the PR is
[here|https://github.com/ccustine/jclouds-labs/commit/35c3a3da451575aa093ef8c0560347dc55ae5c49]
if you want to take a look. I was able to pass live tests without lengthy
timeouts in region FRA1 (which is new and probably less utilized) but still had
issues with others. I'm still wondering if we should add the longer timeouts
permanently for running tests? WDYT?
> Implement the DigitalOcean v2 API
> ---------------------------------
>
> Key: JCLOUDS-613
> URL: https://issues.apache.org/jira/browse/JCLOUDS-613
> Project: jclouds
> Issue Type: New Feature
> Components: jclouds-compute
> Affects Versions: 1.7.3
> Reporter: Ignasi Barrera
> Assignee: Ignasi Barrera
> Labels: digitalocean
> Fix For: 2.0.0
>
>
> DigitalOcean has just released the version 2 of their API. It introduces some
> major changes as long as many improvements and features that make the API
> more easy to consume.
> Version 2 is now a more RESTful API, has a better error population (and hope
> this will help us get rid of the [custom HTTP response parsing
> code|https://github.com/jclouds/jclouds-labs/blob/master/digitalocean/src/main/java/org/jclouds/digitalocean/http/ResponseStatusFromPayloadHttpCommandExecutorService.java#L89-L128]),
> and and a more complete domain model.
> https://www.digitalocean.com/company/blog/api-v2-enters-public-beta/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
