Skip to content

PYTHON Add regression test for AWS credential cache clearing - #3150

Closed
farheenss005 wants to merge 2 commits into
mongodb:mainfrom
farheenss005:fix-aws-auth-cache
Closed

farheenss005 wants to merge 2 commits into
mongodb:mainfrom
farheenss005:fix-aws-auth-cache

Conversation

@farheenss005

@farheenss005 farheenss005 commented Oct 27, 2026 •

Copy link
Copy Markdown

PYTHON Add regression test for AWS credential cache clearing

Changes in this PR

  • Added a regression test in test/asynchronous/test_auth_aws.py.
  • The test covers clearing cached AWS credentials when a connection error occurs during authentication.
  • This change adds test coverage for the expected behavior of asynchronous AWS authentication during connection failures.

Test Plan

  • Ran uv run pytest test/asynchronous/test_auth_aws.py -v.
  • Result: 1 test passed.

Checklist

Checklist for Author

  • Did you update the changelog (if necessary)?
  • Is there test coverage?
  • Is any followup work tracked in a JIRA ticket? If so, add link(s).

Checklist for Reviewer

  • Does the title of the PR reference a JIRA Ticket?
  • Do you fully understand the implementation? (Would you be comfortable explaining how this code works to someone else?)
  • Is all relevant documentation (README or docstring) updated?

@farheenss005
farheenss005 requested a review from a team as a code owner October 27, 2026 02:37
@evergreen-ci-prod

Copy link
Copy Markdown

There is an existing patch(es) for this commit SHA:

Please note that the status that is posted is not in the context of this PR but rather the (latest) existing patch and that may affect some tests that may depend on the particular PR. If your tests do not rely on any PR-specific values (like base or head branch name) then your tests will report the same status. If you would like a patch to run in the context of this PR and abort the other(s), comment 'evergreen retry'.

@NoahStapp

Copy link
Copy Markdown
Contributor

Hi,

Is there a specific bug this test is intended to protect against? A new test without accompanying code changes it verifies is not a pattern of contribution we generally support.

@NoahStapp

Copy link
Copy Markdown
Contributor

Closing due to inactivity. Please re-open with a concrete bug or other issue that this new regression test protects against.

@NoahStapp NoahStapp closed this Nov 5, 2026
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