k2v-client: Add support for native TLS library #560
No reviewers
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#560
Loading…
Reference in New Issue
No description provided.
Delete Branch "jirutka/garage:k2v-native-tls"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
So it can be dynamically linked with the system-provided TLS library instead
of bundling rustls.
f8019cc4ea
tocacb5eb7eb
cacb5eb7eb
tob8342dfaaf
b8342dfaaf
to92a86e3cd1
Can you give me write access to this branch so that I can push an updated
Cargo.nix
file?We can try building this, but I'm pretty sure it will break our CI pipeline. We had a lot of trouble trying to make static builds for all 4 supported architectures and removing openssl entierly was a necessary step to make it work.
Also, if this change is only for k2v-client, why did you also change the dev-dependencies in
src/garage/Cargo.toml
? Maybe without that change we have a chance of building this on our CI, as k2v-client is not built by it.Closing for inactivity.
Pull request closed