gt; {
> "href": "http:\/\/docs.openstack.org
> \/api\/openstack-identity-service\/2.0\/identity-dev-guide-2.0.pdf",
> "type": "application\/pdf",
> "rel": "describedby"
>
On 26/11/13 10:57 -0600, Dolph Mathews wrote:
On Tue, Nov 26, 2013 at 2:47 AM, Flavio Percoco wrote:
As crazy as it sounds, have you guys considered migrating to
Nottingham's approach?
It only sounds crazy because I have no idea how to "migrate" an unversioned
endpoint :) Skimming thro
On Tue, Nov 26, 2013 at 2:47 AM, Flavio Percoco wrote:
> On 25/11/13 16:50 -0600, Dolph Mathews wrote:
>
>>
>> On Mon, Nov 25, 2013 at 2:41 AM, Flavio Percoco
>> wrote:
>>
>>On 25/11/13 09:28 +1000, Jamie Lennox wrote:
>>
>>So the way we have this in keystone at least is that queryin
[openstack-dev] [Keystone][Marconi][Oslo] Discoverable home
document for APIs (Was: Re: [Nova][Glance] Support of v1 and v2 glance APIs in
Nova)
On 25/11/13 16:50 -0600, Dolph Mathews wrote:
>
>On Mon, Nov 25, 2013 at 2:41 AM, Flavio Percoco wrote:
>
>On 25/11/13 09:28 +1000, Jami
On 25/11/13 16:50 -0600, Dolph Mathews wrote:
On Mon, Nov 25, 2013 at 2:41 AM, Flavio Percoco wrote:
On 25/11/13 09:28 +1000, Jamie Lennox wrote:
So the way we have this in keystone at least is that querying GET /
will
return all available API versions and querying /v2
On Mon, Nov 25, 2013 at 2:41 AM, Flavio Percoco wrote:
> On 25/11/13 09:28 +1000, Jamie Lennox wrote:
>
>> So the way we have this in keystone at least is that querying GET / will
>> return all available API versions and querying /v2.0 for example is a
>> similar result with just the v2 endpoint.
uot;: "self"
},
{
"href":
"http:\/\/docs.openstack.org\/api\/openstack-identity-service\/2.0\/content\/",
"type": "text\/html",
"rel": "describedby"
},
{
"
On 25/11/13 09:28 +1000, Jamie Lennox wrote:
So the way we have this in keystone at least is that querying GET / will
return all available API versions and querying /v2.0 for example is a
similar result with just the v2 endpoint. So you can hard pin a version
by using the versioned URL.
I spoke
