chore: unify tls provider#3363
Conversation
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThis PR executes a comprehensive TLS backend migration across the Rust workspace and container images. The root workspace Cargo.toml is updated to configure dependencies with explicit rustls features and add the document_cognition_service/load-test crate. The authentication_service transitions from OpenSSL to the rsa crate for key generation using PKCS#1/PKCS#8 PEM formats. Approximately 20 crates remove their direct openssl dependency, and roughly 18 crates switch redis from tokio-native-tls-comp to tokio-rustls-comp. Additional crates update async-stripe to use the rustls runtime variant, and opensearch is configured to explicitly use rustls-tls. Container images across 10 Dockerfiles drop openssl from their apt package lists, retaining ca-certificates for SSL/TLS validation. Stale cargo-machete and deny.toml entries are cleaned up, and unused build dependencies are removed. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Our workspace has been split on the tls provider backend between rustls and openssl.
This PR consolidates on rustls as the provider of choice because it simplifies the build process and does not require system dependencies.
This should effectively be a noop in terms of behaviour but its a small step in trimming our dep graph.