-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: managed upload not to resolve config repeatedly
Previously the managed upload creates new S3 clients with the constructor parameters of the S3 client used to create the managed upload. That results in that the newly created S3 client needs to resolve every config, including the credentials over and over again. This issue was introduced by #3109 to make sure the internal S3 client inside of managed upload has the same constructor parameters of the S3 client used to create the managed upload. So that the logic relies on the constructor parameters like access point and endpoint discovery works properly. This change supply the resolved client config to create the managed upload internal S3 client so configs don't need to be resolved again, like credentials. Meanwhile, we explicitly set the constructor parameter to be the same as that of S3 client used to create the managed upload.
- Loading branch information
1 parent
f9b1c36
commit f84ff26
Showing
4 changed files
with
31 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
{ | ||
"type": "bugfix", | ||
"category": "ManagedUpload", | ||
"description": "fix a bug that credentials refresh to frequently" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.