Adding the asn field to all GET endpoints that return a server object#7073
Conversation
zrhoffman
left a comment
There was a problem hiding this comment.
LGTM! I'll wait for @ocket8888 to approve before merging (unless he merges it first)
ocket8888
left a comment
There was a problem hiding this comment.
Docs changes all look good (comments are nitpicks), but changes still need to be made to the /servers/{{ID}} endpoint documentation
While fixing the docs of that endpoint, I noticed that those endpoints returning the server structures were not consistent with the api versions they were being called from. So I've fixed that in this PR as well. |
rimashah25
left a comment
There was a problem hiding this comment.
Code changes to get specific version of server object with different version of API call looks good. Tested the changes on localhost with requested selectQuery change and the output was as expected.
rimashah25
left a comment
There was a problem hiding this comment.
Approving the changes for correct server struct response for different version of API calls.
…object (apache#7073) * Adding the field to all endpoints * Adding doc changes * address code review comments * fix testreadservers * fix server representations to be version specific * code review changes
This PR closes #7064 and #7085
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Run Traffic Ops locally.
Make requests for any api version other than
4.1to any endpoint that returns aserverstructure, for example:GET deliveryservices/{id}/servers/eligibleGET deliveryservices/{id}/serversMake sure you do not see the
asnsfield in the response.Run the same test for api version
4.1and make sure that you see theasnsfield in the response this time.Verify that all unit and API tests pass.
If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist