Browse Source

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>
tags/13.0.0.0rc1^2
Sean McGinnis 9 months ago
parent
commit
f41751cb04
No account linked to committer's email address
1 changed files with 2 additions and 4 deletions
  1. 2
    4
      cinder/api/schemas/volume_type_encryption.py

+ 2
- 4
cinder/api/schemas/volume_type_encryption.py View File

@@ -13,10 +13,8 @@
13 13
 #    License for the specific language governing permissions and limitations
14 14
 #    under the License.
15 15
 
16
-"""
17
-Schema for V3 volume type encryption API.
16
+"""Schema for V3 volume type encryption API."""
18 17
 
19
-"""
20 18
 import copy
21 19
 
22 20
 from cinder.api.validation import parameter_types
@@ -35,7 +33,7 @@ create = {
35 33
                            'minLength': 0, 'maxLength': 255},
36 34
             },
37 35
             'required': ['provider', 'control_location'],
38
-            'additionalProperties': False,
36
+            'additionalProperties': True,
39 37
         },
40 38
     },
41 39
     'required': ['encryption'],

Loading…
Cancel
Save