Brandon Logan 6e908dd417 Pecan: Handle member actions ... The legacy pecan uri routing allowed the definition of member actions. These are API resources that hang off a particular resource_id. An example of this is: PUT /routers/{router_id}/add_router_interface The legacy seemed to do only PUTs and GETs so that has been implemented in Pecan. Other methods can easily be added if needed. Also, with the generic handling of this came the decision to remove the specific pecan routers controller because it's only function was to facilitate its member actions to work. It is no longer needed. Change-Id: If776476545edca0c4c43ce3969bb5d1af79f4382		2016-08-30 00:34:02 -05:00
..
__init__.py	Pecan: move fields and filters logic to hooks	2016-06-24 00:38:04 -05:00
body_validation.py	Pecan: bind attribute map to controllers	2016-05-26 06:13:53 +00:00
context.py	Pull project out of request in addition to tenant	2015-12-07 22:16:47 -05:00
notifier.py	Pecan: Handle member actions	2016-08-30 00:34:02 -05:00
ownership_validation.py	Pecan: Streamline request body processing	2016-01-11 04:07:34 -08:00
policy_enforcement.py	Pecan: Handle member actions	2016-08-30 00:34:02 -05:00
query_parameters.py	Pecan: Handle member actions	2016-08-30 00:34:02 -05:00
quota_enforcement.py	Pecan routing for agent schedulers	2016-03-08 06:35:49 +00:00
translation.py	Pecan: remove deprecation warning	2016-05-18 08:41:02 +00:00
utils.py	Pecan: Handle member actions	2016-08-30 00:34:02 -05:00