Changing Traffic Router to point to Traffic Ops api version 5.0#7757
Changing Traffic Router to point to Traffic Ops api version 5.0#7757zrhoffman merged 3 commits intoapache:masterfrom
Conversation
zrhoffman
left a comment
There was a problem hiding this comment.
The hard-coded API versions also need to be changed in the test CrConfigs
traffic_router/core/src/test/resources/publish/CrConfig.json
traffic_router/core/src/test/resources/publish/CrConfig2.json
traffic_router/core/src/test/resources/publish/CrConfig3.json
traffic_router/core/src/test/resources/publish/CrConfig4.json
Yeah just noticed that. Fix has been pushed. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #7757 +/- ##
=========================================
Coverage 31.91% 31.91%
Complexity 98 98
=========================================
Files 712 712
Lines 81875 81875
Branches 965 965
=========================================
Hits 26133 26133
Misses 53596 53596
Partials 2146 2146
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
It changes Traffic Router to point to api 5.0 of Traffic Ops.
Closes: #7658
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Make sure all the tests pass.
Make sure TR works as ecpected in an end to end scenario.
If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist