Cachegroup fallbacks deprecation#3766
Conversation
|
Refer to this link for build results (access rights to CI server needed): |
9565464 to
ce555cd
Compare
|
Refer to this link for build results (access rights to CI server needed): |
mhoppa
left a comment
There was a problem hiding this comment.
The cachegroup_fallbacks endpoints should have a deprecation message added to its response
ce555cd to
55d1375
Compare
done. |
|
Refer to this link for build results (access rights to CI server needed): |
|
retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
|
retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
mhoppa
left a comment
There was a problem hiding this comment.
This looks good - can you fix the merge conflicts and then I will pull down and test it locally for approval
|
Refer to this link for build results (access rights to CI server needed): |
|
retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
|
retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
mhoppa
left a comment
There was a problem hiding this comment.
tested locally and deprecation message looks good and returns on CRUD to cachegroup_fallbacks endpoint
|
retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
What does this PR (Pull Request) do?
Adds a deprecation notice to the
cachegroup_fallbacksTO API endpoint documentation, as discussed in the dev mailing list. Also added missing documentation for thefallbacksproperty of API request/response payloads to/from thecachegroupsandcachegroups/{{ID}}endpoints. Plus I did a little cleaning up of unnamed footnotes and unnecessary escape sequences.Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Build and read the documentation.
The following criteria are ALL met by this PR