Cannot add API extension without tenant_id in the resource

Bug #1573344 reported by Brandon Logan on 2016-04-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
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 Edit Tag help

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

Changed in neutron:
status: New → In Progress

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

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

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

Other bug subscribers