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
When MinioClient is using a custom HTTP client and STS, then the custom HTTP client isn't used for performing the STS request. It will always revert to the default HTTP transport when using credentials.NewSTSAssumeRole (source).
Instead of using credentials.NewSTSAssumeRole, the provider can be created by passing the same HTTP client explicitly, like this:
Although a workaround is possible, this behavior is non-intuitive. Most people would expect the MinIO client to use the specified HTTP transport for all requests that are made on behalf of MinioClient.
The text was updated successfully, but these errors were encountered:
When
MinioClient
is using a custom HTTP client and STS, then the custom HTTP client isn't used for performing the STS request. It will always revert to the default HTTP transport when usingcredentials.NewSTSAssumeRole
(source).Instead of using
credentials.NewSTSAssumeRole
, the provider can be created by passing the same HTTP client explicitly, like this:Although a workaround is possible, this behavior is non-intuitive. Most people would expect the MinIO client to use the specified HTTP transport for all requests that are made on behalf of
MinioClient
.The text was updated successfully, but these errors were encountered: