Skip to content
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

Add credential refresh retry test #3029

Merged
merged 2 commits into from
Mar 5, 2025
Merged

Conversation

lucix-aws
Copy link
Contributor

Adds a "credential refresh" test in the kitchensink service, that explicitly verifies that credentials are re-retrieved when an operation retries.

@lucix-aws lucix-aws requested a review from a team as a code owner March 4, 2025 21:36
}
mhttp := &mockHTTP{
resps: []*http.Response{
{StatusCode: 500, Body: http.NoBody},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's interesting to me that we retry by default on 500. I guess this is because of high availability in services?

@@ -56,6 +62,9 @@ type Options struct {
// used over the deprecated EndpointResolver.
EndpointResolverV2 EndpointResolverV2

// Signature Version 4 (SigV4) Signer
HTTPSignerV4 HTTPSignerV4
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we actually need to have a full auth scheme and v4 signer to test credentials refresh? Would this still work if we had static credentials?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no credentials provider in options without sigv4 or sigv4a (note how the diff shows it was added here)

@lucix-aws lucix-aws merged commit d6db19f into main Mar 5, 2025
13 checks passed
@lucix-aws lucix-aws deleted the credentialretryrefreshtest branch March 5, 2025 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants