jclouds-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ignasi Barrera <n...@apache.org>
Subject Re: DigitalOcean provider still calling v1 API?
Date Mon, 11 Jan 2016 09:07:43 GMT
Oh, you have to change the artifactId of your dependency to "digitalocean2"
too.
El 11/1/2016 9:27 a. m., "Klemen Ferjančič" <imbacen@gmail.com> escribió:

> I tried that but I get: key [digitalocean2] not in the list of providers
> or apis.
>
> On 11. 01. 2016 01:04, Ignasi Barrera wrote:
> > Change your provider to "digitalocean2".
> >
> > It is a different api so you can expect (minor) breaking changes if you
> > are not using the jclouds portable interface.
> >
> > You'll also have to generate an OAuth token in the DigitalOcean console
> > and use it for the credential, since the clientid+apikey authentication
> > has been deprecated too.
> >
> > HTH!
> >
> > I.
> >
> > El 10/1/2016 19:03, "Klemen Ferjančič" <imbacen@gmail.com
> > <mailto:imbacen@gmail.com>> escribió:
> >
> >     Hi
> >
> >     I am trying to do a simple call to list nodes using digitalocean
> >     provider and following the compute-basic example. But I get error:
> "API
> >     v1 has reached end-of-life. Please use API v2."
> >
> >     Server console also shows that jclouds is calling v1 API instead of
> v2:
> >     request=GET
> >     https://api.digitalocean.com/droplets
> >
> >     How is this possible? I checked the jclouds-labs repo and first
> commit
> >     for DigitalOcean 7 months ago was for V2 API so V1 should not even
> exist
> >     in jclouds.
> >
> >     What am I missing? Using jclouds 1.9.1.
> >
>
>

Mime
View raw message