-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate SSL common name #2804
Deprecate SSL common name #2804
Conversation
Codecov ReportBase: 93.57% // Head: 93.42% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #2804 +/- ##
===========================================
- Coverage 93.57% 93.42% -0.15%
===========================================
Files 63 63
Lines 13305 13300 -5
===========================================
- Hits 12450 12426 -24
- Misses 855 874 +19
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, I think this looks good! Let's add a release note entry for this, probably something like:
Enhancement
Endpoints
Discontinued use of sslCommonName hosts as detailed in 1.27.0 (old issue number here)
@nateprewitt just pushed up the changelog. Also should mention I ran integration tests and didn't see any failures. |
* release-1.29.0: Bumping version to 1.29.0 Update to latest models use legacy resolver as source of default region name (#2805) Deprecate SSL common name (#2804) Enable endpoint resolution 2.0 for all services (#2802) Endpoint resolution v2 for Eventbridge (#2788) Supports versioned endpointsV2 files Add test cases for new endpoint models Add endpoint-rule-set-1.json files for every service
This PR formally deprecates the usage of
sslCommonName
in endpoint resolution. This was a legacy codepath back when botocore supported python < 2.7. At this time python did not provide a SSL module, meaning certain certificate formats were needed. Now that new endpoint resolution via ruleset files has been released, this format is no longer necessary.Please see #2705 for additional details.