fix!: use rustls-tls
as default for reqwest
#672
Merged
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.
Closes #671
reqwest
exposes a number of TLS-related features, there is no much sense to re-expose them.Cargo features are additive (and reqwest follows this rule), so it's always possible to customize by adding
reqwest
dependency with desired feature-setWe can re-consider feature-set provided by
testcontainers
later, but currently we already depend on them throughbollard
: it relies onrustls
andrustls-native-certs
It's even possible to make these features optional (e.g when you don't need tls support neither for docker nor reqwest).