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

Ignasi Barrera commented on JCLOUDS-613:
----------------------------------------

Just a heads up: pagination is implemented now in: 
https://github.com/nacx/jclouds-labs/tree/do-pagination, which is forked 
directly from your fork.

There are several other changes in that branch too I found when reading the 
docs to implement the pagination:

* I renamed some classes to DigitalOcean2 to keep consistency with the naming 
of the metadata and api classes.
* I refactored the model so all classes use google auto (like the 
OperatingSystem and Snapshot), and fixed some fields: dates are now Date 
objects, etc. Also aligned all "nullable" annotations with what their docs say.
* Fetched some unit tests from the v1 provider and adapted them to the new one.
* Added a DigitalOcean specific base class for the mock tests.
* Implemented the mock tests for the size, region and action APIs.

I haven't run yet the live tests and it is possible that the changes in the 
model (specifically the nullable thing has broken something), because I want to 
implement all mock tests first. I plan to work on finishing all mock tests this 
week and also implement the remaining API specific live tests that could be 
missing.

> 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