api-ref: project_id/tenant_id in request/response body are shown as "path"

Bug #1650174 reported by Akihiro Motoki
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Akihiro Motoki

Bug Description

project_id/tenant_id in request/response body are shown as "path". They should be "body".
The parameter definition itself is wrong and it affects all resources.
For example, http://developer.openstack.org/api-ref/networking/v2/index.html?expanded=list-routers-detail#list-routers

Tags: api-ref
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron-lib (master)

Fix proposed to branch: master
Review: https://review.openstack.org/411170

Changed in neutron:
status: New → In Progress
Akihiro Motoki (amotoki)
Changed in neutron:
importance: High → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron-lib (master)

Reviewed: https://review.openstack.org/411170
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=318a6b606b4b39e4749691bd020affcd2533499f
Submitter: Jenkins
Branch: master

commit 318a6b606b4b39e4749691bd020affcd2533499f
Author: Akihiro Motoki <email address hidden>
Date: Thu Dec 15 17:38:38 2016 +0900

    api-ref: project_id in req/resp body should be "body"

    project_id and tenant_id field in request/response body are
    marked as "path" now. It should be "body".

    - "project_id-path" already exists and it can be used
      for "project_id" in URL path.
    - "project_id" is now used for body.
    - "project_id-body" is now duplicated, so it was removed.
      fwaas.inc is the only user of project_id-body and
       it is updated accordingly.
    - quotas.inc is updated to use 'project_id-path'.
      Also project_id and tenant_id in response body of a quotas operation
      have been dropped as they do not exist.

    Note that project_id/tenant_id in request body should be marked
    as "optional" in most resources but this patch does not touch them
    to avoid unnecessary merge conflicts.
    They will be fixed in separate patches.

    Change-Id: Ic5a4f55b837ee0a51b7186c3342a94c8c00f6c97
    Closes-Bug: #1650174

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron-lib 1.1.0

This issue was fixed in the openstack/neutron-lib 1.1.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.