Skip to content

build: stop enabling reqwest's native-tls - #10

Draft
jasonhernandez wants to merge 1 commit into
mz_v0.10.xfrom
jason/reqwest-no-native-tls
Draft

jasonhernandez wants to merge 1 commit into
mz_v0.10.xfrom
jason/reqwest-no-native-tls

Conversation

@jasonhernandez

Copy link
Copy Markdown

NOT FOR UPSTREAM. The workspace reqwest dependency no longer enables native-tls, so the fork sets no TLS backend. Materialize enables reqwest's rustls feature itself and installs the aws-lc-rs provider at process startup. That removes openssl, native-tls and hyper-tls from the fork's dependency graph.

This reverses the native-tls part of #5. Materialize is moving its TLS clients off OpenSSL, so the old preference no longer applies.

Risks

Built on its own, the fork has no TLS backend, so HTTPS requests from its own tests or tools fail at connect time. Materialize builds are unaffected because they turn on rustls through feature unification.

Tests

cargo check -p iceberg -p iceberg-catalog-rest passes. No code uses native-tls-specific reqwest APIs.

🤖 Generated with Claude Code

NOT FOR UPSTREAM. Materialize picks reqwest's TLS backend (rustls with the
aws-lc-rs provider) through feature unification, so the fork no longer
forces OpenSSL into every consumer.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant