Walk back deprecation of TO APIv3, add instability warnings for 4.0 #6209
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
ocket8888
added
documentation
rawlinp
approved these changes
Sep 15, 2021
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.
With the recent discussion on the mailing list we've decided to move forward with TO APIv4 being "unstable", which means that APIv3 - being the latest stable version - cannot be deprecated. This PR walks back changes made to deprecate it, and adds a couple of warnings about the instability of TO API v4.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Read the warnings, make sure docs build correctly, etc.
PR submission checklist