Now, in Nailgun, there is a 'weak' create role
validation procedure that only validates JSON schema.
Meanwhile, 'volumes_roles_mapping' ids are not validated,
that allows create roles with wrong 'volumes_roles_mapping'
metadata. This patch:
* fixes validate procedure of 'volumes_roles_mapping' ids
while creating a new role
* moves validate code for already existed roles from handler
to validator
Change-Id: Ib040b9bde0f2a54323a36c8e3c2d01716282cbdc
Closes-Bug: 1619486
(cherry picked from commit a3cd0ea0708e6c532bdcea0ac260c913bddd92f4)
Reviewed: https:/ /review. openstack. org/367983 /git.openstack. org/cgit/ openstack/ fuel-web/ commit/ ?id=deca4979ee3 6fc3dfe14ff029c 325a6e497e50f2
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit deca4979ee36fc3 dfe14ff029c325a 6e497e50f2
Author: tivaliy <email address hidden>
Date: Sun Sep 4 12:24:23 2016 +0300
Align create role validate procedure
Now, in Nailgun, there is a 'weak' create role roles_mapping' ids are not validated, roles_mapping' roles_mapping' ids
validation procedure that only validates JSON schema.
Meanwhile, 'volumes_
that allows create roles with wrong 'volumes_
metadata. This patch:
* fixes validate procedure of 'volumes_
while creating a new role
* moves validate code for already existed roles from handler
to validator
Change-Id: Ib040b9bde0f2a5 4323a36c8e3c2d0 1716282cbdc 32bdcea0ac260c9 13bddd92f4)
Closes-Bug: 1619486
(cherry picked from commit a3cd0ea0708e6c5