feat: allow applications to prune crypto providers #4366
Merged
Conversation
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
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4366 +/- ##
==========================================
+ Coverage 94.87% 94.88% +0.01%
==========================================
Files 189 189
Lines 7217 7217
==========================================
+ Hits 6847 6848 +1
+ Misses 370 369 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
With this change applications can prune the `rustls` crypto providers in all generated clients. The default provider may change over time, but applications can always make a selection by (1) disabling the crypto provider, and then (2) defining what provider to use in their code.
coryan
force-pushed
the
feat-prune-crypto-provider-dependencies-gapics
branch
from
edf4b5b to
1958ffb
Compare
dbolduc
approved these changes
Jan 24, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With this change applications can prune the
rustlscrypto providers in allgenerated clients. The default provider may change over time, but applications
can always make a selection by (1) disabling the crypto provider, and then (2)
defining what provider to use in their code.
Fixes #4237