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

Fix Retries for ECSCredentialsProvider #259

Merged
merged 6 commits into from
Jan 21, 2025
Merged

Fix Retries for ECSCredentialsProvider #259

merged 6 commits into from
Jan 21, 2025

Conversation

waahm7
Copy link
Contributor

@waahm7 waahm7 commented Jan 8, 2025

Description of changes:

  • Add retries to ECSCredentialsProvider

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@@ -71,6 +75,25 @@ struct aws_credentials_provider_ecs_user_data {
int error_code;
};

/* called in between retries. */
static void s_ecs_user_data_reset_request_specific_data(struct aws_credentials_provider_ecs_user_data *user_data) {
Copy link
Contributor

Choose a reason for hiding this comment

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

There's another similarly named pre-existing function in this file: s_aws_credentials_provider_ecs_user_data_reset_response()

What's the difference? Can they be combined? If not, put them next to each other with a comment explaining when you'd call one and not the other.

If there's already some kind of reset function in this file ... did we miss some other flow that should be reporting record_success() (or failure)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, I have removed the other function since it was not needed. We will call the new function between retries to clear the request level data.

@waahm7 waahm7 merged commit 5bc6779 into main Jan 21, 2025
34 checks passed
@waahm7 waahm7 deleted the ecs-retries branch January 21, 2025 23:40
github-merge-queue bot pushed a commit to awslabs/mountpoint-s3 that referenced this pull request Jan 23, 2025
Update the CRT to the latest releases.

This change also updates the exclude list, primarily due to one of the
test files being replaced by a compressed (but still large) file:
aws/aws-lc#2123

This change pulls in a bug fix
(awslabs/aws-c-auth#259), addressing
#1207.

### Does this change impact existing behavior?

One bug fix is included in CRT changes.

### Does this change need a changelog entry? Does it require a version
change?

Change log entry added for the CRT fix. It is a bug fix, so patch
version bump to `mountpoint-s3-client` remains appropriate.

---

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license and I agree to the terms of
the [Developer Certificate of Origin
(DCO)](https://developercertificate.org/).

Signed-off-by: Daniel Carl Jones <[email protected]>
keremnc pushed a commit to keremnc/mountpoint-s3 that referenced this pull request Jan 24, 2025
Update the CRT to the latest releases.

This change also updates the exclude list, primarily due to one of the
test files being replaced by a compressed (but still large) file:
aws/aws-lc#2123

This change pulls in a bug fix
(awslabs/aws-c-auth#259), addressing
awslabs#1207.

### Does this change impact existing behavior?

One bug fix is included in CRT changes.

### Does this change need a changelog entry? Does it require a version
change?

Change log entry added for the CRT fix. It is a bug fix, so patch
version bump to `mountpoint-s3-client` remains appropriate.

---

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license and I agree to the terms of
the [Developer Certificate of Origin
(DCO)](https://developercertificate.org/).

Signed-off-by: Daniel Carl Jones <[email protected]>
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