Revert RESOLVED_CHECKSUM_SPECS mapping for SRA #4621
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.
Motivation and Context
Fix for #4608.
Modifications
This is reverting the read/write mapping logic for checksum related execution attribute (RESOLVED_CHECKSUM_SPECS) that was introduced in https://github.com/aws/aws-sdk-java-v2/pull/4452/files#diff-933c20d96318c11c8224fcd3904f17bad1614606bd1d934e17bb719d99b183be to support SRA SignerProperty for the same. With this revert, flexible checksums (used only by SRA) will to not work with useSraAuth=true, but this is a minimal fix to resolve the issue, and we can make a different fix with SRA support later.
Testing
Ran regular tests in CI, as well as integration/stability tests.
Screenshots (if appropriate)
Types of changes
Checklist
mvn install
succeedsscripts/new-change
script and following the instructions. Commit the new file created by the script in.changes/next-release
with your changes.License