|
1 | 1 | <!-- Do not manually edit this file, use `update-changelogs` --> |
| 2 | +0.7.0 (February 18th, 2022) |
| 3 | +=========================== |
| 4 | +**Breaking Changes:** |
| 5 | +- ⚠ ([smithy-rs#1144](https://github.com/awslabs/smithy-rs/issues/1144)) The `aws_config::http_provider` module has been renamed to `aws_config::http_credential_provider` to better reflect its purpose. |
| 6 | +- ⚠ ([smithy-rs#1144](https://github.com/awslabs/smithy-rs/issues/1144)) Some APIs required that timeout configuration be specified with an `aws_smithy_client::timeout::Settings` struct while |
| 7 | + others required an `aws_smithy_types::timeout::TimeoutConfig` struct. Both were equivalent. Now `aws_smithy_types::timeout::TimeoutConfig` |
| 8 | + is used everywhere and `aws_smithy_client::timeout::Settings` has been removed. Here's how to migrate code your code that |
| 9 | + depended on `timeout::Settings`: |
| 10 | + |
| 11 | + The old way: |
| 12 | + ```rust |
| 13 | + let timeout = timeout::Settings::new() |
| 14 | + .with_connect_timeout(Duration::from_secs(1)) |
| 15 | + .with_read_timeout(Duration::from_secs(2)); |
| 16 | + ``` |
| 17 | + |
| 18 | + The new way: |
| 19 | + ```rust |
| 20 | + // This example is passing values, so they're wrapped in `Option::Some`. You can disable a timeout by passing `None`. |
| 21 | + let timeout = TimeoutConfig::new() |
| 22 | + .with_connect_timeout(Some(Duration::from_secs(1))) |
| 23 | + .with_read_timeout(Some(Duration::from_secs(2))); |
| 24 | + ``` |
| 25 | +- ⚠ ([smithy-rs#1144](https://github.com/awslabs/smithy-rs/issues/1144)) `MakeConnectorFn`, `HttpConnector`, and `HttpSettings` have been moved from `aws_config::provider_config` to |
| 26 | + `aws_smithy_client::http_connector`. This is in preparation for a later update that will change how connectors are |
| 27 | + created and configured. |
| 28 | + |
| 29 | + If you were using these structs/enums, you can migrate your old code by importing them from their new location. |
| 30 | +- ⚠ ([smithy-rs#1144](https://github.com/awslabs/smithy-rs/issues/1144)) Along with moving `HttpConnector` to `aws_smithy_client`, the `HttpConnector::make_connector` method has been renamed to |
| 31 | + `HttpConnector::connector`. |
| 32 | + |
| 33 | + If you were using this method, you can migrate your old code by calling `connector` instead of `make_connector`. |
| 34 | +- ⚠ ([smithy-rs#1085](https://github.com/awslabs/smithy-rs/issues/1085)) Moved the following re-exports into a `types` module for all services: |
| 35 | + - `aws_sdk_<service>::AggregatedBytes` -> `aws_sdk_<service>::types::AggregatedBytes` |
| 36 | + - `aws_sdk_<service>::Blob` -> `aws_sdk_<service>::types::Blob` |
| 37 | + - `aws_sdk_<service>::ByteStream` -> `aws_sdk_<service>::types::ByteStream` |
| 38 | + - `aws_sdk_<service>::DateTime` -> `aws_sdk_<service>::types::DateTime` |
| 39 | + - `aws_sdk_<service>::SdkError` -> `aws_sdk_<service>::types::SdkError` |
| 40 | +- ⚠ ([smithy-rs#1085](https://github.com/awslabs/smithy-rs/issues/1085)) `AggregatedBytes` and `ByteStream` are now only re-exported if the service has streaming operations, |
| 41 | + and `Blob`/`DateTime` are only re-exported if the service uses them. |
| 42 | +- ⚠ ([smithy-rs#1130](https://github.com/awslabs/smithy-rs/issues/1130)) MSRV increased from `1.54` to `1.56.1` per our 2-behind MSRV policy. |
| 43 | +- ⚠ ([smithy-rs#1132](https://github.com/awslabs/smithy-rs/issues/1132)) Fluent clients for all services no longer have generics, and now use `DynConnector` and `DynMiddleware` to allow |
| 44 | + for connector/middleware customization. This should only break references to the client that specified generic types for it. |
| 45 | + |
| 46 | + If you customized the AWS client's connector or middleware with something like the following: |
| 47 | + ```rust |
| 48 | + let client = aws_sdk_s3::Client::with_config( |
| 49 | + aws_sdk_s3::client::Builder::new() |
| 50 | + .connector(my_custom_connector) // Connector customization |
| 51 | + .middleware(my_custom_middleware) // Middleware customization |
| 52 | + .default_async_sleep() |
| 53 | + .build(), |
| 54 | + config |
| 55 | + ); |
| 56 | + ``` |
| 57 | + Then you will need to wrap the custom connector or middleware in |
| 58 | + [`DynConnector`](https://docs.rs/aws-smithy-client/0.36.0/aws_smithy_client/erase/struct.DynConnector.html) |
| 59 | + and |
| 60 | + [`DynMiddleware`](https://docs.rs/aws-smithy-client/0.36.0/aws_smithy_client/erase/struct.DynMiddleware.html) |
| 61 | + respectively: |
| 62 | + ```rust |
| 63 | + let client = aws_sdk_s3::Client::with_config( |
| 64 | + aws_sdk_s3::client::Builder::new() |
| 65 | + .connector(DynConnector::new(my_custom_connector)) // Now with `DynConnector` |
| 66 | + .middleware(DynMiddleware::new(my_custom_middleware)) // Now with `DynMiddleware` |
| 67 | + .default_async_sleep() |
| 68 | + .build(), |
| 69 | + config |
| 70 | + ); |
| 71 | + ``` |
| 72 | + |
| 73 | + If you had functions that took a generic connector, such as the following: |
| 74 | + ```rust |
| 75 | + fn some_function<C, E>(conn: C) -> Result<()> |
| 76 | + where |
| 77 | + C: aws_smithy_client::bounds::SmithyConnector<Error = E> + Send + 'static, |
| 78 | + E: Into<aws_smithy_http::result::ConnectorError> |
| 79 | + { |
| 80 | + // ... |
| 81 | + } |
| 82 | + ``` |
| 83 | + |
| 84 | + Then the generics and trait bounds will no longer be necessary: |
| 85 | + ```rust |
| 86 | + fn some_function(conn: DynConnector) -> Result<()> { |
| 87 | + // ... |
| 88 | + } |
| 89 | + ``` |
| 90 | + |
| 91 | + Similarly, functions that took a generic middleware can replace the generic with `DynMiddleware` and |
| 92 | + remove their trait bounds. |
| 93 | + |
| 94 | +**New this release:** |
| 95 | +- 🐛 ([aws-sdk-rust#443](https://github.com/awslabs/aws-sdk-rust/issues/443)) The `ProfileFileRegionProvider` will now respect regions set in chained profiles |
| 96 | +- ([smithy-rs#1144](https://github.com/awslabs/smithy-rs/issues/1144)) Several modules defined in the `aws_config` crate that used to be declared within another module's file have been moved to their own files. The moved modules are `sts`, `connector`, and `default_providers`. They still have the exact same import paths. |
| 97 | +- 🐛 ([smithy-rs#1129](https://github.com/awslabs/smithy-rs/issues/1129)) Fix some docs links not working because they were escaped when they shouldn't have been |
| 98 | +- ([smithy-rs#1085](https://github.com/awslabs/smithy-rs/issues/1085)) The `Client` and `Config` re-exports now have their documentation inlined in the service docs |
| 99 | +- 🐛 ([smithy-rs#1180](https://github.com/awslabs/smithy-rs/issues/1180)) Fixed example showing how to use hardcoded credentials in `aws-types` |
| 100 | + |
| 101 | + |
2 | 102 | 0.6.0 (January 26, 2022) |
3 | 103 | ======================== |
4 | 104 | **New this release:** |
|
0 commit comments