AWS: Make sure Signer + User Agent config are both applied #10198
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.
This fixes an issue where the remote signing configuration is being overriden/ignored when the user-agent configuration is being applied. This is because calling
overrideConfiguration(Consumer<ClientOverrideConfiguration.Builder> overrideConfiguration)creates a newClientOverrideConfigurationand ignores any existing ones that might have been set previously.The
s3RemoteSigningEnabledWithUserAgent()test reproduces the issue and fails without the fix being proposed here.