[ 
https://issues.apache.org/jira/browse/JCLOUDS-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604429#comment-14604429
 ] 

Chris Custine commented on JCLOUDS-613:
---------------------------------------

That would make sense.  I was able to get them to pass yesterday with the 
timeouts increased so I'm not so worried at this point.  I'm going to remove 
them locally and create the PR now.

> 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)

Reply via email to