Skip to content

Conversation

cenedhryn
Copy link
Contributor

Modifications

  • Disables MD5 checksum when S3 CRT native client is created.
  • MD5 checksum parameter is added to the native configuration in order to use it more easily if needed
  • Propagates the resolved checksum specification to the async client

Testing

  • Verifies an async request with the SDK checksum algorithm set will translate to the correct checksum

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed
  • I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

@cenedhryn cenedhryn requested a review from a team as a code owner July 18, 2022 20:28
@sonarqubecloud
Copy link

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 76 Code Smells

76.4% 76.4% Coverage
6.9% 6.9% Duplication

@cenedhryn cenedhryn force-pushed the salande/tm-disable-md5 branch from 1d99639 to 44f27b6 Compare July 21, 2022 15:20
@joviegas
Copy link
Contributor

Did we do a integ testing and check if the requests are succeeded ?

ChecksumSpecs checksumSpecs = asyncRequest.httpExecutionAttributes().getAttribute(CHECKSUM_SPECS);
if (checksumSpecs != null && checksumSpecs.algorithm() != null) {
Algorithm checksumAlgorithm = checksumSpecs.algorithm();
switch (checksumAlgorithm) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use Enum.fromValue(str.toUpper/LowerCase) here instead of switch case ?

@@ -160,10 +161,11 @@ public void afterMarshalling(Context.AfterMarshalling context,
SdkHttpExecutionAttributes.builder()
.put(OPERATION_NAME,
executionAttributes.getAttribute(SdkExecutionAttribute.OPERATION_NAME))
.put(CHECKSUM_SPECS,
executionAttributes.getAttribute(SdkExecutionAttribute.RESOLVED_CHECKSUM_SPECS))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see we do a

getAttribute(SdkExecutionAttribute.RESOLVED_CHECKSUM_SPECS)

where is SdkExecutionAttribute.RESOLVED_CHECKSUM_SPECS updated with resolved in case of code flow for transfer manager execution ?

@zoewangg
Copy link
Contributor

Closing in favor of #3376

@zoewangg zoewangg closed this Aug 24, 2022
@cenedhryn cenedhryn deleted the salande/tm-disable-md5 branch September 9, 2022 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants