Skip to content

DRAFT feat: allow setting or unsetting the boto retry configuration #1271

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

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ryancausey
Copy link
Contributor

DRAFT feature for #1268

@ryancausey
Copy link
Contributor Author

@ikonst this is my first attempt at adding this feature. I wanted to check that this was in line with what we discussed in #1268 before polishing and adding tests. Please review and let me know, thanks!

@ryancausey ryancausey force-pushed the feat/add-boto-compatible-retry-configuration branch from 6ac73a6 to 1fb386b Compare May 21, 2025 05:16
@ryancausey ryancausey force-pushed the feat/add-boto-compatible-retry-configuration branch from 1fb386b to 8705eb6 Compare May 21, 2025 05:21
@ryancausey
Copy link
Contributor Author

The good news is this change works locally for me and confirms that botocore is handling the AWS SDK configuration discovery logic, not boto3. I was able to override the setting to be None and it automatically picked up the retry configuration values in my ~/.aws/config file.

@ryancausey ryancausey force-pushed the feat/add-boto-compatible-retry-configuration branch from 8705eb6 to a741b8d Compare May 23, 2025 23:40
@ryancausey ryancausey force-pushed the feat/add-boto-compatible-retry-configuration branch from a741b8d to 64b9ee2 Compare May 23, 2025 23:44
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.

1 participant