keystone/keystone/resource
liyingjun 3dfc046375 Fix KeyError when rename to a name is already in use
When a user attempts to rename a project via the PATCH
v3/projects/{project_id} API, and the new name is already in-use, rather
than return a nice error explaining that the name is in use, keystone
blows up and raises `KeyError: 'is_domain'` in
_generate_project_name_conflict_msg.

Change-Id: I56fcd8fe1258e2d1de3e541144649ef619f86a7b
Closes-bug: #1565108
(cherry picked from commit c1be6883f2)
2016-04-14 17:57:42 +00:00
..
V8_backends Use the new enginefacade from oslo.db 2016-02-24 08:20:12 -08:00
backends Deprecate domain driver interface methods 2016-03-01 09:01:30 +00:00
config_backends Use the new enginefacade from oslo.db 2016-02-24 08:20:12 -08:00
__init__.py Remove exposure of routers at package level 2015-12-03 15:06:56 -03:00
controllers.py Merge "V2 operations create default domain on demand" 2016-03-02 10:32:20 +00:00
core.py Fix KeyError when rename to a name is already in use 2016-04-14 17:57:42 +00:00
routers.py Support the reading of default values of domain configuration options 2016-01-15 06:20:38 +00:00
schema.py Projects acting as domains 2016-03-01 00:42:44 +00:00