On Thursday, July 31, 2014, Russell Bryant <rbry...@redhat.com> wrote:
> On 07/30/2014 10:57 AM, Dolph Mathews wrote: > > We recently merged an implementation for GET /v3/catalog which finally > > enables POST /v3/auth/tokens?nocatalog to be a reasonable default > > behavior, at the cost of an extra HTTP call from remote service back to > > keystone where necessary. > > Is that really a safe default change to make? It looks like v3 has > already been marked as stable, and this would be a non > backwards-compatible change to the API. > > This default could be made in keystone client, and the catalog could be fetched separately (session object can handle it). It would mean new clients would get the same data without a massive token size, but old clients would still be compatible. API remains compatible and stable. Cheers, Morgan
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
