delta003 opened a new issue, #318: URL: https://github.com/apache/arrow-rs-object-store/issues/318
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] (This section helps Arrow developers understand the context and *why* for this feature, in addition to the *what*) --> I need to customize request signing when talking to S3-compatible APIs. **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> Be able to provide a signer implementation to AmazonS3Builder that is used by AwsAuthorizer / replaces AwsAuthorizer, similar to https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-core/src/main/java/com/amazonaws/auth/Signer.java#L24 It can be a small part of authorizer or all of it, but I'm curious how you think about the design of this crate and if this is or isn't something you'd consider. AwsAuthorizer supports overriding session token name ``` /// Overrides the header name for security tokens, defaults to `x-amz-security-token` pub(crate) fn with_token_header(mut self, header: HeaderName) -> Self { self.token_header = Some(header); self } ``` but this struct is very deep in the design, so this isn't configurable to a user. Even just being able to configure the token name could work for me. **Describe alternatives you've considered** <!-- A clear and concise description of any alternative solutions or features you've considered. --> There are some discussions in OpenDAL to support customizable signer, backed by reqsign crate. **Additional context** <!-- Add any other context or screenshots about the feature request here. --> I'd be happy to propose a refactor in the PR as long as there is a chance to get it merged - don't want to waste time if this goes against your design principles for the crate. Thank you. -- 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]
