Allow extra parameters in volume_type_encryption

Change I6488cc89e60a31605ddf80c7aa56ddf4871d3c1a added schema validation
for volume type encryption, but it locked things down in a non-backwards
compatible way by not allowing extra parameters. This has caused
problems for at least Horizon. If we are going change this to not be
backwards compatible it should include a microversion bump and moving
the endpoint out of contrib to a standard endpoint.

To keep some schema validation at least, this just allows extra
parameters so existing API consumers should be unaffected. We can
address locking things down better in a future release when we have time
to do it right.

Closes-bug: #1783467
Closes-bug: #1786054

Change-Id: I45c254eca69471509e7ae4c957df51282e2d1776
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This commit is contained in:
Sean McGinnis 2018-08-08 14:34:22 -05:00
parent a27d0eb32a
commit f41751cb04
No known key found for this signature in database
GPG Key ID: CE7EE4BFAF8D70C8
1 changed files with 2 additions and 4 deletions

View File

@ -13,10 +13,8 @@
# License for the specific language governing permissions and limitations
# under the License.
"""
Schema for V3 volume type encryption API.
"""Schema for V3 volume type encryption API."""
"""
import copy
from cinder.api.validation import parameter_types
@ -35,7 +33,7 @@ create = {
'minLength': 0, 'maxLength': 255},
},
'required': ['provider', 'control_location'],
'additionalProperties': False,
'additionalProperties': True,
},
},
'required': ['encryption'],