yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #51542
[Bug 1570259] Re: Pecan: 'fields' query parameter not handled anywhere
Reviewed: https://review.openstack.org/305707
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=80426cf6201374588f0118365992905eddce268e
Submitter: Jenkins
Branch: master
commit 80426cf6201374588f0118365992905eddce268e
Author: salvatore <salv.orlando@xxxxxxxxx>
Date: Thu Apr 14 11:34:04 2016 +0200
Pecan: tell the plugin about field selection
Neutron plugin are able to do field selection on responses (for
instance only returning id & name for a resource). However,
Pecan does not leverage this capability and always tells the
plugin to fetch all fields, doing field selection while
processing the response.
This patch ensures that pecan send the field list down to the
plugin.
As a part of this patch TestRequestProcessing has been update
to inherit from TestRootController rather than
TestResourceController. Inheriting from the latter was causing
tests to be executed twice for no reason, beyong using
TestResourceController's 'port' attribute, which was however
unnecessary as this change proves.
Closes-Bug: #1570259
Change-Id: Iac930cd3bb14dfdda78e6a94d2c8bef2b5c4b9a5
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1570259
Title:
Pecan: 'fields' query parameter not handled anywhere
Status in neutron:
Fix Released
Bug description:
The pecan framework currently does not handle properly the 'fields'
query parameter as when specifiied it is not sent down to the plugin.
Instead field selection happens while processing the response.
This is not entirely wrong, but since plugins have the capability of
doing field selection they should allowed to use it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1570259/+subscriptions
References