Public bug reported: As discussed in [1], the
POST /v2.0/agents/{agent_id}/l3-routers does not return a response body. This seems inconsistent with our other APIs as POSTs typically return the created resource. This is even true with other APIs that 'add' something to a resource. It seems we should consider returning the resource here; I suspect it's just a few LOC changes in the API. [1] https://review.openstack.org/#/c/543408/6/api-ref/source/v2/l3 -agent-scheduler.inc@76 ** Affects: neutron Importance: Undecided Status: New ** Tags: api -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1762733 Title: l3agentscheduler doesn't return a response body with POST /v2.0/agents/{agent_id}/l3-routers Status in neutron: New Bug description: As discussed in [1], the POST /v2.0/agents/{agent_id}/l3-routers does not return a response body. This seems inconsistent with our other APIs as POSTs typically return the created resource. This is even true with other APIs that 'add' something to a resource. It seems we should consider returning the resource here; I suspect it's just a few LOC changes in the API. [1] https://review.openstack.org/#/c/543408/6/api-ref/source/v2/l3 -agent-scheduler.inc@76 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1762733/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp