Attribute filtering should be based on all objects instead of only first
Bug #1829414 reported by
Tom Stappaerts
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
In Progress
|
Medium
|
Tom Stappaerts | ||
Bug Description
When returning a resource from neutron the resouce attribute are filtered based on the current policy and the attributes defined in the resource definition.
Currently on the first object in a list of objects to be returned is checked, if it happens that there are other objects in the list that have additional attributes, those are not checked at all.
I believe all attributes should be checked. Since this originally changed from checking all to only checking the first in a "efficiency of api" commit, I will propose a patchset that has minimal impact while still fixing the issue; please provide feedback here or on gerrit.
| Changed in neutron: | |
| assignee: | nobody → Tom Stappaerts (tstappae) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to neutron (master) | #1 |
| Changed in neutron: | |
| status: | New → In Progress |
| Changed in neutron: | |
| importance: | Undecided → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on neutron (master) | #2 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/