nova/nova/api/openstack/placement/schemas
Chris Dent 0fc4f95914 [placement] disallow additional fields in allocations
Back in microversion 1.12, when the allocations structure was extended
to allow project_id and user_id on PUT /allocations/{uuid},
"additionalProperties" was not set in the JSON schema, so it has been
possible since then to include unused fields in the input. The schema
was then reused in the creation of subsequent schema for new
microversions and for new URIs, such as POST /allocations and the
forthcoming /reshaper.

This change fixes it by fixing the old microversion. This is the "just
fix it" option from the discussion on the associated bug. The other
option is to create a new microversion that corrects the behavior. This
is more complex than it might initially sound because of the way in
which the original schema is used to compose new ones.

Change-Id: Ied464744803864e61a45e03c559760a8a2e2581f
Closes-Bug: #1782340
2018-07-19 10:46:13 +01:00
..
__init__.py [placement] Separate API schemas (usage) 2017-12-14 15:15:33 +00:00
aggregate.py placement: generation in provider aggregate APIs 2018-03-14 17:08:52 -05:00
allocation_candidate.py placement: Granular GET /allocation_candidates 2018-05-08 11:54:30 -05:00
allocation.py [placement] disallow additional fields in allocations 2018-07-19 10:46:13 +01:00
inventory.py Move db MAX constants to own file 2018-03-01 11:09:29 +00:00
resource_class.py [placement] Separate API schemas (resource_class) 2017-12-17 01:01:58 +00:00
resource_provider.py rp: GET /resource_providers?required=<traits> 2018-02-23 12:08:32 -06:00
trait.py [placement] Separate API schemas (trait) 2017-12-14 15:16:01 +00:00
usage.py [placement] Separate API schemas (usage) 2017-12-14 15:15:33 +00:00