[openstack-dev] [openstack-tc] Proposal for API version discovery

Jay Pipes jaypipes at gmail.com
Tue May 28 14:41:24 UTC 2013


On 05/28/2013 10:36 AM, Martyn Taylor wrote:
> Hi all,
> 
> I am currently looking at the Ironic API and was pointed towards the
> etherpad here: 
> https://etherpad.openstack.org/api-version-discovery-proposal
> 
> With regards to version discovery I wonder why do we not treat the API
> and the Version simply like any other resource and have them completely
> discoverable.  An example of how I originally had this is shown here:
> https://gist.github.com/mtaylor/5663143//.  The example here uses the
> same concepts across the whole of the API.  Therefore there is no need
> to add in extra pieces such as response code 300 with some specific
> document.  The API including versions are fully discoverable and treat
> like any other resource.  To save complexity the API defaults to the
> most recent version should a version not be specified in either the MIME
> type or URL.
> 
> What are your thoughts?  Is there some use case where this approach will
> not work.

Seems eminently workable to me.

-jay



More information about the OpenStack-dev mailing list