yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53956
[Bug 1596754] Re: Pecan controllers should construct the plugin method names similar to how the legacy wsgi does
Reviewed: https://review.openstack.org/334736
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a2016a6211806763c9060f2df4c9dc4736c2146b
Submitter: Jenkins
Branch: master
commit a2016a6211806763c9060f2df4c9dc4736c2146b
Author: Brandon Logan <brandon.logan@xxxxxxxxxxxxx>
Date: Mon Jun 27 21:17:12 2016 -0500
Pecan: Define plugin crud methods in base class
Refactors the current pecan code to use predefined methods to get
the plugin methods the controllers will call. This also adds in
parent resource information to build those method names, but parent
support will not be complete until a follow up patch.
Change-Id: I4e0e6ef96364991a9393bc5fba495e37dade68a1
Closes-Bug: #1596754
** 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/1596754
Title:
Pecan controllers should construct the plugin method names similar to
how the legacy wsgi does
Status in neutron:
Fix Released
Bug description:
Currently, pecan will construct the name of the plugin methods that
will be called per controller method right before it is called. In
the legacy wsgi, those methods are already constructed at startup.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1596754/+subscriptions
References