jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Custine (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-613) Implement the DigitalOcean v2 API
Date Tue, 05 May 2015 23:22:59 GMT

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

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

This sounds like a great plan.  I just rebased on master and ran live tests with all upstream
jclouds changes and have 2 new failures since last time I ran them I will take a look at those,
but other than that, everything seems to be working great.  I will also take a look at the
API changes and see if anything needs to be updated/added.

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

Mime
View raw message