srijeet0406 opened a new issue, #7064: URL: https://github.com/apache/trafficcontrol/issues/7064
<!-- ************ STOP!! ************ If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact the Apache Traffic Control Security Team at [email protected] and follow the guidelines at https://apache.org/security regarding vulnerability disclosure. - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request) or the Traffic Control Users mailing list (send an email to [email protected] to subscribe). - Before submitting, please **SEARCH GITHUB** for a similar issue or PR * https://github.com/apache/trafficcontrol/issues * https://github.com/apache/trafficcontrol/pulls --> <!-- Do not submit security vulnerabilities or support requests here - see above --> ## This Bug Report affects these Traffic Control components: <!-- delete all those that don't apply --> - Traffic Ops ## Current behavior: <!-- Describe how the bug happens --> After https://github.com/apache/trafficcontrol/pull/7023 was merged, some endpoints that return the represenation of a server in the response don't have the ASN field accounted for. These routes will need a `4.1` api version equivalent, so that these new routes can account for the new field. ## Expected behavior: <!-- Describe what the behavior would be without the bug --> All 3.1 routes should return a consistent representation of a server object. ## Steps to reproduce: <!-- If the current behavior is a bug, please provide the *STEPS TO REPRODUCE* and include the applicable TC version. --> Except for the `GET /api/4.1/servers` endpoint, all other 4.1 routes return a server representation that does not have the `asns` field in it. This needs to be fixed so that all routes return the same server object representation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
