Allow using reqwest and rustls without pulling in OpenSSL/native-tls

[faysou]

Bug Report

Expected Behavior

Issue: The databento crate always leads to using native-tls with reqwest which can lead to compilation problems with other crates.

Expected behaviour is being able to use rustls with other crates and reqwest.

With the reqwest configuration below I don't have this issue, I vendored databento to be able to modify it in my project.

If you used this config in the databento-rs Cargo.toml, I wouldn't need to vendor databento.

Also if someone has a native-tls requirement for reqwest in their project, cargo feature unification would be able to use native-tls with reqwest anyway. Basically reqwest very easily defaults to using rustls and native-tls, but using rustls only doesn't require openssl installed and avoids potential linking issues with openssl (I know, I've been working on this for full three days with a lot of help from an LLM agent as well).

reqwest = { workspace = true, optional = true, default-features = false, features = ["json", "stream", "rustls-tls"] }

Actual Behavior

reqwest always always pulls reqwest native-tls and rustls when using databento

Steps to Reproduce the Problem

1. Have a crate that is configured to use rustls like object_store
2. Use databento as well
3. See that the dependencies with cargo tree always pull native-tls, this can create linking issues with openssl in a github runner. With rustls, openssl is not required.

Specifications

• OS platform: Ubuntu 22.4
• Rust version: latest
• databento version: latest

[threecgreen]

I'm not going to change the default TLS used for the historical client, but I'll make the usage of reqwest's default-tls feature flag optional so one can avoid pulling in OpenSSL if desired.

[faysou]

This makes sense so the following would work I think in the databento-rs cargo.toml:

reqwest = { version = "0.12", optional = true, default-features = false, features = ["json", "stream"] }

I will test this solution now on my side.
Edit: yes, using default-features = false as a few lines above works.

I'm looking forward then to a new minor release of your library so I can release my feature soon, thank you.

[threecgreen]

Resolved in 2b7292d, which will be released later today as part of 0.27.0

[faysou]

Thank you for the quick update.