Thanks for the answer, cdent, and the discussion on IRC [1]. In summary:
- Those links are the full `path` component of the resource, to which
one would prepend the protocol://server:port to get its fully-qualified
location. The '/placement' prefix is determined and included by the web
server,
On Fri, 11 Aug 2017, Eric Fried wrote:
I finally got around to fiddling with the placement API today, and
noticed something... disturbing. To me, anyway.
When I GET a URI, such as '/resource_classes', the response includes e.g.
I assume you're using ksa/requests somewhere in your stack and
I finally got around to fiddling with the placement API today, and
noticed something... disturbing. To me, anyway.
When I GET a URI, such as '/resource_classes', the response includes e.g.
{u'links': [{u'href': u'/placement/resource_classes/MEMORY_MB',
u'rel': u'self'}],
u'name':
