JakeDern opened a new pull request, #462:
URL: https://github.com/apache/arrow-rs-object-store/pull/462
# Which issue does this PR close?
Closes #413.
# Rationale for this change
Many companies, including my current employer, are picky about what
cryptographic implementations may be used. This PR seeks to accomplish two
things:
1. Make it possible to have no default crypto provider, such as ring, in the
dependency tree
2. Make it possible to bring your own crypto provider
# What changes are included in this PR?
This is heavily WIP - I'm just opening this to make it clear how the
approach with generic types would work vs an implementation that would use
`dyn` instead at the expense of having to allocate and copy the outputs of
various crypto implementations.
- Add a `CryptoProvider` trait
- Add an optional `RingProvider` implementation based on the `ring` feature
# Are there any user-facing changes?
Yes, several including:
- Making builders for clouds that need crypto generic
- Making `default::Default` implementations dependent on the `ring` feature
- Making `new()` require a crypto provider
<!---
If there are any breaking changes to public APIs, please call them out.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
