Skip to content
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

Make reqwest an optional feature #7203

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

tustvold
Copy link
Contributor

Which issue does this PR close?

Closes #.

Rationale for this change

POC showing that the abstractions added in #7183 allow reqwest to be an optional feature.

I'm not entirely sure whether we should merge this, it seems unfortunate to force users to opt-in to reqwest, but it at least shows that this is possible

What changes are included in this PR?

Are there any user-facing changes?

@github-actions github-actions bot added the object-store Object Store Interface label Feb 26, 2025
@@ -195,8 +198,10 @@ impl FromStr for ClientConfigKey {
/// This is used to configure the client to trust a specific certificate. See
/// [Self::from_pem] for an example
#[derive(Debug, Clone)]
#[cfg(feature = "reqwest")]
Copy link
Contributor Author

@tustvold tustvold Feb 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the only remaining place where reqwest leaks into the public API, this is somewhat hard to get away from because of its intertwining with the TLS machinery of reqwest.

@tustvold tustvold force-pushed the make-reqwest-optional branch from 0f35094 to 370cae7 Compare February 26, 2025 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
object-store Object Store Interface
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant