Skip to content

Commit

Permalink
Merge smithy-rs-release-1.x.y into main (#3969)
Browse files Browse the repository at this point in the history
  • Loading branch information
aws-sdk-rust-ci authored Jan 15, 2025
2 parents f7f037d + 9303ce1 commit 5c2757d
Show file tree
Hide file tree
Showing 6 changed files with 167 additions and 165 deletions.
13 changes: 0 additions & 13 deletions .changelog/1736370747.md

This file was deleted.

10 changes: 0 additions & 10 deletions .changelog/flexible-checksums-client.md

This file was deleted.

12 changes: 0 additions & 12 deletions .changelog/flexible-checksums-s3.md

This file was deleted.

10 changes: 10 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,14 @@
<!-- Do not manually edit this file. Use the `changelogger` tool. -->
January 14th, 2025
==================
**New this release:**
- :bug::tada: (client, [smithy-rs#3845](https://github.com/smithy-lang/smithy-rs/issues/3845)) S3 client behavior is updated to always calculate a checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). The default checksum algorithm is CRC32. Checksum behavior can be configured using `when_supported` and `when_required` options - in shared config using request_checksum_calculation, or as env variable using AWS_REQUEST_CHECKSUM_CALCULATION.

The S3 client attempts to validate response checksums for all S3 API operations that support checksums. However, if the SDK has not implemented the specified checksum algorithm then this validation is skipped. Checksum validation behavior can be configured using `when_supported` and `when_required` options - in shared config using response_checksum_validation, or as env variable using AWS_RESPONSE_CHECKSUM_VALIDATION.
- :bug::tada: (client, [smithy-rs#3967](https://github.com/smithy-lang/smithy-rs/issues/3967)) Updates client generation to conform with Smithy's updates to the [httpChecksum trait](https://smithy.io/2.0/aws/aws-core.html#aws-protocols-httpchecksum-trait).
- :bug: (client, [aws-sdk-rust#1234](https://github.com/awslabs/aws-sdk-rust/issues/1234)) Fix token bucket not being set for standard and adaptive retry modes


December 30th, 2024
===================

Expand Down
32 changes: 30 additions & 2 deletions aws/SDK_CHANGELOG.next.json
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
"author": "Velfi",
"references": [],
"since-commit": "039177d0ee6dd288ad57de2230a1110bbe7ff7d5",
"age": 4
"age": 5
},
{
"message": "It is now possible to disable payload signing through an operation customization.\n\n```rust\nasync fn put_example_object(client: &aws_sdk_s3::Client) {\n let res = client\n .put_object()\n .bucket(\"test-bucket\")\n .key(\"test-key\")\n .body(ByteStream::from_static(b\"Hello, world!\"))\n .customize()\n // Setting this will disable payload signing.\n .disable_payload_signing()\n .send()\n .await;\n}\n```\n\nDisabling payload signing will result in a small speedup at the cost of removing a data integrity check.\nHowever, this is an advanced feature and **may not be supported by all services/operations**.\n",
Expand All @@ -29,7 +29,35 @@
"smithy-rs#3583"
],
"since-commit": "89881abd3df80e9b6fd59790d7c02e2b9a6dd45c",
"age": 3
"age": 4
},
{
"message": "Fix token bucket not being set for standard and adaptive retry modes\n",
"meta": {
"bug": true,
"breaking": false,
"tada": false
},
"author": "aajtodd",
"references": [
"aws-sdk-rust#1234"
],
"since-commit": "f7f037d3fda2d02b6a2ad1bce40dd84c787c6c35",
"age": 1
},
{
"message": "S3 client behavior is updated to always calculate a checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). The default checksum algorithm is CRC32. Checksum behavior can be configured using `when_supported` and `when_required` options - in shared config using request_checksum_calculation, or as env variable using AWS_REQUEST_CHECKSUM_CALCULATION.\n\nThe S3 client attempts to validate response checksums for all S3 API operations that support checksums. However, if the SDK has not implemented the specified checksum algorithm then this validation is skipped. Checksum validation behavior can be configured using `when_supported` and `when_required` options - in shared config using response_checksum_validation, or as env variable using AWS_RESPONSE_CHECKSUM_VALIDATION.\n",
"meta": {
"bug": true,
"breaking": false,
"tada": true
},
"author": "landonxjames",
"references": [
"smithy-rs#3845"
],
"since-commit": "f7f037d3fda2d02b6a2ad1bce40dd84c787c6c35",
"age": 1
}
],
"aws-sdk-model": []
Expand Down
Loading

0 comments on commit 5c2757d

Please sign in to comment.