heat/heat/api
Steve Baker 759b46259c Map the NotFound exception to HTTPNotFound
Now if the DB API raises a NotFound which propagates
to the REST response, the user will receive a 404.

This seems to be a better default behaviour than a 500,
and other behaviours can be handled by catching NotFound
in service.py

This change is needed for the SoftwareDeployment resource
to do our usual ignore-404-on-handle_delete behaviour.

Change-Id: If00c4de41dc24f462af0b32b29cd6d70f314f3bf
2014-01-31 16:47:46 +13:00
..
aws Fixes typo of explanation on exception.py 2014-01-03 10:21:01 +08:00
cfn Fix unused variables 2/2: enable unused var check 2014-01-08 18:01:05 +08:00
cloudwatch Fix unused variables 2/2: enable unused var check 2014-01-08 18:01:05 +08:00
middleware Map the NotFound exception to HTTPNotFound 2014-01-31 16:47:46 +13:00
openstack New middleware to handle SSL termination proxies 2014-01-14 15:58:14 -03:00
__init__.py Empty files shouldn't contain copyright nor license 2013-12-24 20:29:31 +08:00