V1 API additionalParams value should not be converted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
Fix Released
|
Medium
|
Unassigned |
Bug Description
[Problem]
In the V1 API, if "additionalParams" dict is included in the request body, the value will be converted from camelCase to snake_case as follows:
Example input body:
{
"additionalPa
"FirstKey": "FirstValue",
"SecondKey": "SecondKey"
}
}
--> converted body:
{
"additional_
"first_key": "FirstValue",
"second_key": "SecondKey"
}
}
This "additionalPara
[Cause]
For example, `utils.
[Fix proposal]
In the `utils.
The `utils.
Note that `additionalParams` and `additional_params` themselves require conversion.
[1] https:/
[2] https:/
[3] https:/
Changed in tacker: | |
status: | New → In Progress |
Changed in tacker: | |
importance: | Undecided → Medium |
Reviewed: https:/ /review. opendev. org/c/openstack /tacker/ +/838660 /opendev. org/openstack/ tacker/ commit/ 0e68a316059a379 09dc279bca5d2c0 aab8c4f82d
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 0e68a316059a379 09dc279bca5d2c0 aab8c4f82d
Author: Ayumu Ueha <email address hidden>
Date: Wed Apr 20 08:39:42 2022 +0000
Change to not convert additionalParams of V1 API
The value of additionalParams of request or response data that is
user-defined data should not be converted during processing.
This patch changes to not convert value of additionalParams in request
or additional_params in response.
Closes-Bug: #1969704 6e8ea2e43a708c7 0ac623e17e5
Change-Id: Ie652adc521e2c5