Added deprecation notices for /user/current/update#3954
Conversation
|
Refer to this link for build results (access rights to CI server needed): |
mhoppa
left a comment
There was a problem hiding this comment.
I am getting this result when running it
{
"alerts": [
[
{
"level": "success",
"text": "User profile was successfully updated"
}
],
{
"level": "warning",
"text": "This endpoint is deprecated, please use 'PUT /api/1.4/user/current' instead"
}
]
}
The deprecation object should be in the alert list
|
Well, actually, it is. The success message is in a sub-list for some reason. I'll try to figure out why it's doing that. |
442f1b4 to
61ae113
Compare
|
This took hours to figure out. Turns out, [ is VERY different from ( in Perl. |
|
Refer to this link for build results (access rights to CI server needed): |
mhoppa
left a comment
There was a problem hiding this comment.
Works as expected. Looks like an accidental docker change came in so need to revert that.
61ae113 to
75821e8
Compare
|
Refer to this link for build results (access rights to CI server needed): |
What does this PR (Pull Request) do?
Adds deprecation notices for the
/user/current/updateto all responses from that endpoint as well as to the documentation.Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Make requests to the
/user/current/updateendpoint and notice the new warning-level alert indicating its deprecation.Also, build and read the documentation.
The following criteria are ALL met by this PR