mattjackson220 opened a new issue #6701: URL: https://github.com/apache/trafficcontrol/issues/6701
<!-- ************ 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 Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components: <!-- delete all those that don't apply --> - Traffic Ops (maybe) - Traffic Router ## Current behavior: <!-- Describe how the current features are insufficient. --> Currently, the Watchers in Traffic Router (like LetsEncryptDnsChallengeWatcher and FederationsWatcher) have the Traffic Ops API version hard coded. ## New behavior: <!-- Describe how this change would improve Traffic Control --> This should be updated to be a parameter so a new deployment isnt required to change API versions. The new behavior should just use a changeable API version instead of the hardcoded one -- 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]
