fix(util-endpoints): augment endpointFunctions inline in endpointResolver functions #5933
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
Related to #5925
#5889
#5435
Description
This changes the way we register
awsEndpointFunctions
. Instead of callingWe will do this in each individual client's endpointResolver fn:
This aims to work around two issues:
import "@aws-sdk/util-endpoints";
because it looks like it's unused, even though it's being imported for its side-effects.@smithy/util-endpoints
is duplicated due to multiple versions being depended upon, one of those may not receive the augmentation. By running it inline with the client's code, this ensures that whatever version of@smithy/util-endpoints
being used by the client is augmented by the same.Testing
integration tests cover this, because without the AWS endpoint functions, integration tests will fail, due to being unable to resolve endpoints.