test(nested-clients): add defaultProvider assertion #7292
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
*.integ.spec.ts
).@public
tag and enable doc generation on the package?