jpappa200 opened a new issue, #7768: URL: https://github.com/apache/trafficcontrol/issues/7768
<!-- ************ STOP!! ************ If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact the Apache Traffic Control Security Team at secur...@trafficcontrol.apache.org 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 users-subscr...@trafficcontrol.apache.org 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 Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components: <!-- delete all those that don't apply --> - Traffic Control Cache Config (`t3c`, formerly ORT) ## Current behavior: <!-- Describe how the current features are insufficient. --> Currently t3c will use traffic ops API v4 and fall back to v3 if v4 is unavailable ## New behavior: <!-- Describe how this change would improve Traffic Control --> t3c will use traffic ops API v5 by default and fall back to v4 if v5 is unavailable -- 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: issues-unsubscr...@trafficcontrol.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
