-
Notifications
You must be signed in to change notification settings - Fork 916
Auth: Respect async credentials update flag from DefaultCredentialsProvider for WebIdentityTokenFileCredentialProvider #3899
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
0118a7f
to
3c208ef
Compare
…eCredentialProvider
3c208ef
to
5f49149
Compare
Thanks for the pull request! I notice there are some Error while running unit-tests:
Please provide a fix and we can then complete the review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update tests in software.amazon.awssdk.services.sts.internal.WebIdentityTokenCredentialProviderTest#createAssumeRoleWithWebIdentityTokenCredentialsProviderViaProfileSucceeds
Hey @L-Applin, thanks for your time. Please take another look. |
SonarCloud Quality Gate failed. |
@all-contributors please add @paulolieuthier for code. |
I've put up a pull request to add @paulolieuthier! 🎉 |
Thanks! Looking forward to the next release. |
Motivation and Context
Despite having the flag and implementation ready, WebIdentityTokenFileCredentialProvider used through DefaultCredentialsProvider cannot have the async credentials update feature enabled, because the flag is not passed through, contrary to how it's done with other providers.
Allowing async credentials update enables clients running in environments like Kubernetes to avoid refreshing credentials in request-time, which causes latency spikes.
Modifications
Testing
The modification was easy to validate because the latency spikes are gone after the patch.
Types of changes
Checklist
mvn install
succeedsscripts/new-change
script and following the instructions. Commit the new file created by the script in.changes/next-release
with your changes.License