yahoo-eng-team team mailing list archive

[Tom Stappaerts <1829414@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
     Assignee: Tom Stappaerts (tstappae)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Tom Stappaerts (tstappae)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1829414

Title:
  Attribute filtering should be based on all objects instead of only
  first

Status in neutron:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1829414/+subscriptions