keystone/keystone/resource
Dave Chen 295cfde14c No need the redundant validation in manager level
Alone with the enabling of schema validation for V2 API, the property
validation has been handled in controller level, property validation
based on clean.py in manager level is no long needed for creating a
project since schema validation is enabled for both V2 and V3.

The patch removes the call from `clean.py` and remove the relevant
testcases since we already have the testcases both in
`test_validation.py` or `test_v2_validation.py`.

Partially implements: bp schema-validation-extent

Change-Id: I9d2ea60d496d83372109ca227ee2091850de0213
2016-07-28 04:36:39 +00:00
..
V8_backends Move the resource abstract base class out of core 2016-05-02 13:30:51 +00:00
backends Replace keystone.common.config with keystone.conf package 2016-06-24 17:02:15 +00:00
config_backends Replace keystone.common.config with keystone.conf package 2016-06-24 17:02:15 +00:00
__init__.py Remove exposure of routers at package level 2015-12-03 15:06:56 -03:00
controllers.py Add schema validation to v2 create tenant 2016-07-27 03:47:07 +00:00
core.py No need the redundant validation in manager level 2016-07-28 04:36:39 +00:00
routers.py Remove unnecessary stable attribute value for status 2016-07-09 08:20:32 -07:00
schema.py Add schema validation to v2 create tenant 2016-07-27 03:47:07 +00:00