This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Add TO API v5#7063
Merged
srijeet0406 merged 14 commits intoapache:masterfrom Sep 13, 2022
Merged
Conversation
ocket8888
added
new feature
ocket8888
force-pushed
the
to/api-v5
branch
2 times, most recently
from
7d6292d to
dcf44b8
Compare
srijeet0406
reviewed
Sep 10, 2022
Contributor
There was a problem hiding this comment.
Shouldn't this have the Unstable section that you removed from the v4-client/ README.md?
Contributor
Author
There was a problem hiding this comment.
No, TO APIv5 is not released, so it doesn't need that notice. APIv2 and APIv3 didn't have it, for example.
(cherry picked from commit a70d6282e68213383b8491ff0e8315450df79296)
(cherry picked from commit 523b13a0fa946571003f20e6a0342c4701a0017f)
(cherry picked from commit 8592b498ba21110f5e51021b7021569e0591c846)
Also bumps default from now-deprecated 3.0 to current 4.1
ocket8888
force-pushed
the
to/api-v5
branch
from
dcf44b8 to
b039a60
Compare
srijeet0406
approved these changes
Sep 13, 2022
5 tasks
4 tasks
zrhoffman
pushed a commit
to zrhoffman/trafficcontrol
that referenced
this pull request
Oct 2, 2022
* Add APIv5 routes (cherry picked from commit a70d6282e68213383b8491ff0e8315450df79296) * Add v5 API client (cherry picked from commit 523b13a0fa946571003f20e6a0342c4701a0017f) * Add APIv5 docs (cherry picked from commit 8592b498ba21110f5e51021b7021569e0591c846) * Remove instability notice from client that's no longer unstable * Remove outdated instability notice * Add APIv5 support to the client Also bumps default from now-deprecated 3.0 to current 4.1 * Add APIv5 to tests * Update CHANGELOG * Fix rebase issues * Fix incorrect typing * fix broken reference * Fix malformed table * Fix duplicate label * Fix incorrect user-agent
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds version 5.0 of the Traffic Ops API.
Everything still uses v4 (which doesn't matter yet as there are no differences between v4 and v5 as of this PR)
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Make sure all of the new APIv5 TO Go client integration tests pass, make sure the docs build without errors or warnings and are complete and accurate.
PR submission checklist