Skip to content

test(nested-clients): add defaultProvider assertion#7292

Merged
kuhe merged 1 commit into
aws:mainfrom
kuhe:chore/nested-sts
Aug 28, 2025
Merged

test(nested-clients): add defaultProvider assertion#7292
kuhe merged 1 commit into
aws:mainfrom
kuhe:chore/nested-sts

Conversation

@kuhe

@kuhe kuhe commented Aug 28, 2025

Copy link
Copy Markdown
Contributor

Issue

n/a

Description

I noticed that the custom rewrite of the nested STS client removes the credentialDefaultProvider. Because that is a critical element of the nested client, I'm adding this unit test as an early detection.

It's possible that a regression here would be detected by our other tests, such as credentials integration, but this small additional test won't hurt.

Checklist

  • [n/a] If the PR is a feature, add integration tests (*.integ.spec.ts).
  • [n/a] If you wrote E2E tests, are they resilient to concurrent I/O?
  • [n/a] If adding new public functions, did you add the @public tag and enable doc generation on the package?

@kuhe kuhe requested a review from a team as a code owner August 28, 2025 20:44
@kuhe kuhe changed the title test(nestd-clients): add defaultProvider assertion test(nested-clients): add defaultProvider assertion Aug 28, 2025
@kuhe kuhe merged commit f560a39 into aws:main Aug 28, 2025
2 checks passed
@kuhe kuhe deleted the chore/nested-sts branch August 28, 2025 20:50
@github-actions

Copy link
Copy Markdown

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Sep 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants