You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not currently possible to enable or disable request signing via ClientLogMode API Client Options on individual operations. This configuration can only be provided when the API Client is first initialized, and only if a custom HTTPSignerV4 is not provided. (Its OK that the log option is ignored if custom signer is used.)
Issues
There is also no way to enable LogSigning per operation call because the addHTTPSignerV4Middleware does not pass down logging level.
The default v4 signer's LogSigning is only modified when when API client is created without custom HTTPSignerV4.
When an Operation is invoked and the addHTTPSignerV4Middleware helper is run to add the signing middleware, the helper takes functional parameters instead of a structure. This would make it impossible to add additional parameters in the future without using a different middleware helper in the v4 package.
Update v4.NewSignHTTPRequestMiddleware to take structure for options instead of individual function parameters. This will allow future options to be passed down from the operation's adding the middleware.
Update the HTTPSignerV4, and HTTPSigner interfaces to to functional options for additional signing options such as LogSigning. Adding a , optFns ...func(*v4.SignerOptions) to the signature.
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
It is not currently possible to enable or disable request signing via
ClientLogMode
API ClientOptions
on individual operations. This configuration can only be provided when the API Client is first initialized, and only if a customHTTPSignerV4
is not provided. (Its OK that the log option is ignored if custom signer is used.)Issues
There is also no way to enable
LogSigning
per operation call because theaddHTTPSignerV4Middleware
does not pass down logging level.The default v4 signer's
LogSigning
is only modified when when API client is created without custom HTTPSignerV4.aws-sdk-go-v2/service/s3/api_client.go
Lines 215 to 226 in 3f8ff9a
When an Operation is invoked and the
addHTTPSignerV4Middleware
helper is run to add the signing middleware, the helper takes functional parameters instead of a structure. This would make it impossible to add additional parameters in the future without using a different middleware helper in the v4 package.aws-sdk-go-v2/service/s3/api_client.go
Lines 207 to 209 in 3f8ff9a
aws-sdk-go-v2/aws/signer/v4/middleware.go
Lines 204 to 207 in 3f8ff9a
The
HTTPSignerV4
API client generated interface does not provide functional options for additional configurations.aws-sdk-go-v2/service/s3/api_client.go
Lines 211 to 213 in 3f8ff9a
Proposal
Update
v4.NewSignHTTPRequestMiddleware
to take structure for options instead of individual function parameters. This will allow future options to be passed down from the operation's adding the middleware.Update the
HTTPSignerV4
, andHTTPSigner
interfaces to to functional options for additional signing options such asLogSigning
. Adding a, optFns ...func(*v4.SignerOptions)
to the signature.The text was updated successfully, but these errors were encountered: