aws-smithy-types-convert changelog and release notes | crates.io

NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →

0.42.013 May 2022

⚠🎉 (aws-sdk-rust#494, aws-sdk-rust#519) The aws_smithy_http::byte_stream::bytestream_util::FsBuilder has been updated to allow for easier creation of

Breaking Changes:

⚠🎉 (aws-sdk-rust#494, aws-sdk-rust#519) The aws_smithy_http::byte_stream::bytestream_util::FsBuilder has been updated to allow for easier creation of multi-part requests.

FsBuilder::offset is a new method allowing users to specify an offset to start reading a file from.
FsBuilder::file_size has been reworked into FsBuilder::length and is now used to specify the amount of data to read.

With these two methods, it's now simple to create a ByteStream that will read a single "chunk" of a file. The example below demonstrates how you could divide a single File into consecutive chunks to create multiple ByteStreams.

let example_file_path = Path::new("/example.txt");
let example_file_size = tokio::fs::metadata(&example_file_path).await.unwrap().len();
let chunks = 6;
let chunk_size = file_size / chunks;
let mut byte_streams = Vec::new();

for i in 0..chunks {
    let length = if i == chunks - 1 {
        // If we're on the last chunk, the length to read might be less than a whole chunk.
        // We substract the size of all previous chunks from the total file size to get the
        // size of the final chunk.
        file_size - (i * chunk_size)
    } else {
        chunk_size
    };

    let byte_stream = ByteStream::read_from()
        .path(&file_path)
        .offset(i * chunk_size)
        .length(length)
        .build()
        .await?;

    byte_streams.push(byte_stream);
}

for chunk in byte_streams {
    // Make requests to a service
}

New this release:

(smithy-rs#1352) Log a debug event when a retry is going to be peformed
(smithy-rs#1332, @82marbag) Update generated crates to Rust 2021

Contributors Thank you for your contributions! ❤

@82marbag (smithy-rs#1332)

Open source →

0.39.017 Mar 2022

⚠ (aws-sdk-rust#406) aws_types::Config has been renamed to aws_types:sdk_config::SdkConfig. This is to better differentiate it from service-specific c

Breaking Changes:

⚠ (aws-sdk-rust#406) aws_types::config::Config has been renamed to aws_types:sdk_config::SdkConfig. This is to better differentiate it from service-specific configs like aws_s3_sdk::Config. If you were creating shared configs with aws_config::load_from_env(), then you don't have to do anything. If you were directly referring to a shared config, update your use statements and struct names.

Before:
```
use aws_types::config::Config;

fn main() {
    let config = Config::builder()
    // config builder methods...
    .build()
    .await;
}
```
After:
```
use aws_types::SdkConfig;

fn main() {
    let config = SdkConfig::builder()
    // config builder methods...
    .build()
    .await;
}
```
⚠ (smithy-rs#724) Timeout configuration has been refactored a bit. If you were setting timeouts through environment variables or an AWS profile, then you shouldn't need to change anything. Take note, however, that we don't currently support HTTP connect, read, write, or TLS negotiation timeouts. If you try to set any of those timeouts in your profile or environment, we'll log a warning explaining that those timeouts don't currently do anything.

If you were using timeouts programmatically, you'll need to update your code. In previous versions, timeout configuration was stored in a single TimeoutConfig struct. In this new version, timeouts have been broken up into several different config structs that are then collected in a timeout::Config struct. As an example, to get the API per-attempt timeout in previous versions you would access it with <your TimeoutConfig>.api_call_attempt_timeout() and in this new version you would access it with <your timeout::Config>.api.call_attempt_timeout(). We also made some unimplemented timeouts inaccessible in order to avoid giving users the impression that setting them had an effect. We plan to re-introduce them once they're made functional in a future update.

New this release:

(smithy-rs#1225) DynMiddleware is now cloneable
(smithy-rs#1257) HTTP request property bag now contains list of desired HTTP versions to use when making requests. This list is not currently used but will be in an upcoming update.

Open source →

0.37.021 Feb 2022

⚠ (smithy-rs#1144) Some APIs required that timeout configuration be specified with an aws_smithy_client::Settings struct while others required an aws_

Breaking Changes:

⚠ (smithy-rs#1144) Some APIs required that timeout configuration be specified with an aws_smithy_client::timeout::Settings struct while others required an aws_smithy_types::timeout::TimeoutConfig struct. Both were equivalent. Now aws_smithy_types::timeout::TimeoutConfig is used everywhere and aws_smithy_client::timeout::Settings has been removed. Here's how to migrate code your code that depended on timeout::Settings:

The old way:
```
let timeout = timeout::Settings::new()
    .with_connect_timeout(Duration::from_secs(1))
    .with_read_timeout(Duration::from_secs(2));
```
The new way:
```
// This example is passing values, so they're wrapped in `Option::Some`. You can disable a timeout by passing `None`.
let timeout = TimeoutConfig::new()
    .with_connect_timeout(Some(Duration::from_secs(1)))
    .with_read_timeout(Some(Duration::from_secs(2)));
```
⚠ (smithy-rs#1085) Moved the following re-exports into a types module for all services:
- <service>::AggregatedBytes -> <service>::types::AggregatedBytes
- <service>::Blob -> <service>::types::Blob
- <service>::ByteStream -> <service>::types::ByteStream
- <service>::DateTime -> <service>::types::DateTime
- <service>::SdkError -> <service>::types::SdkError
⚠ (smithy-rs#1085) AggregatedBytes and ByteStream are now only re-exported if the service has streaming operations, and Blob/DateTime are only re-exported if the service uses them.
⚠ (smithy-rs#1130) MSRV increased from 1.54 to 1.56.1 per our 2-behind MSRV policy.

New this release:

(smithy-rs#1144) MakeConnectorFn, HttpConnector, and HttpSettings have been moved from aws_config::provider_config to aws_smithy_client::http_connector. This is in preparation for a later update that will change how connectors are created and configured.
(smithy-rs#1123) Refactor Document shape parser generation
(smithy-rs#1085) The Client and Config re-exports now have their documentation inlined in the service docs

Open source →