Matt Riedemann 6f5b3123cc Fix 'force' parameter in os-quota-sets PUT schema ... A regression was introduced in the 2.36 API microversion where the 'force' parameter was missing from the 'PUT /os-quota-sets/{tenant_id}' API request schema so users could not force quota updates with microversion 2.36 or later. The bug is now fixed so that the 'force' parameter can once again be specified during quota updates. There is no new microversion for this change since it is an admin-only API. Change-Id: I947e927802f755ccb25a91efd82cac895779d19e Closes-Bug: #1733886 (cherry picked from commit 9ddbaa15cb)		2017-12-07 09:39:07 -05:00
..
v2.36	Fix 'force' parameter in os-quota-sets PUT schema	2017-12-07 09:39:07 -05:00
quotas-show-defaults-get-resp.json	Add 'networks' quota in quota sample files	2017-07-04 23:45:30 +00:00
quotas-show-detail-get-resp.json	Add 'networks' quota in quota sample files	2017-07-04 23:45:30 +00:00
quotas-show-get-resp.json	Add 'networks' quota in quota sample files	2017-07-04 23:45:30 +00:00
quotas-update-force-post-req.json	Move the v2 api_sample functional tests	2015-08-18 15:25:41 +08:00
quotas-update-force-post-resp.json	Add 'networks' quota in quota sample files	2017-07-04 23:45:30 +00:00
quotas-update-post-req.json	Move the v2 api_sample functional tests	2015-08-18 15:25:41 +08:00
quotas-update-post-resp.json	Add 'networks' quota in quota sample files	2017-07-04 23:45:30 +00:00
user-quotas-show-get-resp.json	Add 'networks' quota in quota sample files	2017-07-04 23:45:30 +00:00
user-quotas-update-post-req.json	Move the v2 api_sample functional tests	2015-08-18 15:25:41 +08:00
user-quotas-update-post-resp.json	Add 'networks' quota in quota sample files	2017-07-04 23:45:30 +00:00