[openstack-dev] [keystone] endpoint versioning in API v3
Mac Innes, Kiall
kiall at hp.com
Tue Jan 29 15:51:48 UTC 2013
I've had similar thoughts before myself.
IMO, The catalog should return version-less endpoints where those
endpoints return a "300 Multiple Choice".
The extra HTTP request is going to be painful though, in an attempt to
remain practical, a supportedVersions list could be returned by keystone.
Thanks,
Kiall
On 29/01/13 15:46, Jay Pipes wrote:
> I think versionList is pointless, as you mention above the proper way of
> handling this is a 300 Multiple Choice response on the base endpoint.
> The endpoints themselves should be the source of truth about what
> versions of an API they expose or support. Keystone, IMHO, should merely
> be a directory of endpoints/services, not a directory of endpoints and
> API versions on an endpoint.
More information about the OpenStack-dev
mailing list