This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Remove the addition of the 4.1 TO API version#6297
Merged
mattjackson220 merged 1 commit intoapache:masterfrom Oct 18, 2021
Merged
Remove the addition of the 4.1 TO API version#6297mattjackson220 merged 1 commit intoapache:masterfrom
mattjackson220 merged 1 commit intoapache:masterfrom
Conversation
The 4.0 TO API version is currently considered unstable and under development, so the addition of a 4.1 TO API version was unnecessary. New TO API changes can currently be made to 4.0. This is a follow-up to apache#6282 which included the addition of 4.1.
rawlinp
added
Traffic Ops
mattjackson220
approved these changes
Oct 18, 2021
Contributor
mattjackson220
left a comment
mattjackson220
left a comment
There was a problem hiding this comment.
code looks good, tests pass, and local testing passes!
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.
The 4.0 TO API version is currently considered unstable and under
development, so the addition of a 4.1 TO API version was unnecessary.
New TO API changes can currently be made to 4.0.
This is a follow-up to #6282 which included the addition of 4.1.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Mostly taken from #6282:
Create a certificate that has SANs and add it to a delivery service (or use one that already exists)
Verify that on the certificate page in TP there is a field for the SANs and that it is filled in appropriately.
Verify that the deliveryservices/xmlId/{xmlid}/sslkeys endpoint returns the SANs for API version
4.14.0 but does not for any previous versionVerify that the TO tests pass
PR submission checklist