chore(middleware): make base64Encoder/Decoder optional #4138
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
Internal JS-3705
util-base64 implementation added in #4137
Description
Attempt to make base64Encoder Optional. This would require lot of testing, as multiple middleware had assumed base64Encoder to be present. Also, it would break customers who might have written middleware and using base64Encoder /base64Decoder set in clients.
Will set base64Encoder/base64Decoder from
@aws-sdk/util-base64
in runtimeConfig of clients instead.Testing
N/A
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.