Add a page that addresses migrating from Traffic Ops API v1 for each endpoint #5344
Conversation
This file contains 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
zrhoffman
added
documentation
zrhoffman
force-pushed
the
api-v1-migration-page
branch
2 times, most recently
from
e335906
to
6694bbe
Compare
|
Rebased to fix a merge conflict |
ocket8888
approved these changes
Dec 4, 2020
zrhoffman
force-pushed
the
api-v1-migration-page
branch
from
6694bbe
to
2fa85c7
Compare
|
Rebased to resolve merge conflicts |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR (Pull Request) do?
This PR adds a table that users can refer to when updating their Traffic Ops clients from API version 1.x. It tells you which v3 endpoint to use for each v1 endpoint.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
/api/migrating-from-v1.htmlThe following criteria are ALL met by this PR