Cannot add API extension without tenant_id in the resource

Bug #1573344 reported by Brandon Logan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Won't Fix
Undecided
Brandon Logan

Bug Description

Sometimes an API extension that defines a new resource without a tenant_id is wanted. Currently, the validation code assumes tenant_id is supposed to be on every resource, so even if the extension does not define tenant_id as an attribute in the resource's body, the validation layer will throw an error saying it was passed in.

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

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

Changed in neutron:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Brandon Logan (<email address hidden>) on branch: master
Review: https://review.openstack.org/309235
Reason: not really wanted

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by Brandon Logan (<email address hidden>) on branch: master
Review: https://review.openstack.org/309235

Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

Bug closed due to lack of activity, please feel free to reopen if needed.

Changed in neutron:
status: In Progress → Won't Fix
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.