yahoo-eng-team team mailing list archive

[Dolph Mathews <1309243@xxxxxxxxxxxxxxxxxx>]

This looks a lot like a call we'd *like* to have in v3 (perhaps GET
/v3/catalog + X-Subject-Token), but we don't implement anything like
this in v2.

** Changed in: keystone
       Status: New => Triaged

** Changed in: keystone
   Importance: Undecided => Medium

** Project changed: keystone => openstack-api-site

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1309243

Title:
  API v2 - tenantId in list token endpoints response

Status in OpenStack API documentation site:
  Triaged

Bug description:
  This API (GET v2.0/tokens/{tokenId}/endpoints ) is documented in the v2 APIs (http://api.openstack.org/api-ref-identity.html#identity-v2)
   
  The documented response example is :
   {
   "endpoints":[
   { "id":1, "tenantId":"1", "region":"North", "type":"compute", "publicURL":"https://compute.north.public.com/v1";, "internalURL":"https://compute.north.internal.com/v1";, "adminURL":"https://compute.north.internal.com/v1";, "versionId":"1", "versionInfo":"https://compute.north.public.com/v1/";, "versionList":"https://compute.north.public.com/"; },
   { "id":2, "tenantId":"1", "region":"South", "type":"compute", "publicURL":"https://compute.north.public.com/v1";, "internalURL":"https://compute.north.internal.com/v1";, "adminURL":"https://compute.north.internal.com/v1";, "versionId":"1", "versionInfo":"https://compute.north.public.com/v1/";, "versionList":"https://compute.north.public.com/"; },
   { "id":3, "tenantId":"1", "region":"East", "type":"compute", "publicURL":"https://compute.north.public.com/v1";, "internalURL":"https://compute.north.internal.com/v1";, "adminURL":"https://compute.north.internal.com/v1";, "versionId":"1", "versionInfo":"https://compute.north.public.com/v1/";, "versionList":"https://compute.north.public.com/"; },
   { "id":4, "tenantId":"1", "region":"West", "type":"compute", "publicURL":"https://compute.north.public.com/v1";, "internalURL":"https://compute.north.internal.com/v1";, "adminURL":"https://compute.north.internal.com/v1";, "versionId":"1", "versionInfo":"https://compute.north.public.com/v1/";, "versionList":"https://compute.north.public.com/"; },
  { "id":5, "tenantId":"1", "region":"Global", "type":"compute", "publicURL":"https://compute.north.public.com/v1";, "internalURL":"https://compute.north.internal.com/v1";, "adminURL":"https://compute.north.internal.com/v1";, "versionId":"1", "versionInfo":"https://compute.north.public.com/v1/";, "versionList":"https://compute.north.public.com/"; } 
  ],
   "endpoints_links":[

  ]
   }

  In reality, we don't have "tenantId" in response.  This looks like a
  v2 api documentation issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-api-site/+bug/1309243/+subscriptions