Breaking Changes
CredentialsError
variants became non-exhaustive & now have struct bodies. This makes them impossible to construct directly outside of theaws_types
crate. In order to construct credentials errors, new methods have been added for each variant. Instead ofCredentialsError::Unhandled(...)
, you should instead useCredentialsError::unhandled
. Matching methods exist for all variants. If you match on specific variants, you will also need to update your code to include..
. (#781)- The default credentials chain now returns
CredentialsError::CredentialsNotLoaded
instead ofProviderError
when no credentials providers are configured. - ⚠️ All Smithy runtime crates have been renamed to have an
aws-
prefix. This may require code changes:- Cargo.toml changes:
smithy-async
->aws-smithy-async
smithy-client
->aws-smithy-client
smithy-eventstream
->aws-smithy-eventstream
smithy-http
->aws-smithy-http
smithy-http-tower
->aws-smithy-http-tower
smithy-json
->aws-smithy-json
smithy-protocol-test
->aws-smithy-protocol-test
smithy-query
->aws-smithy-query
smithy-types
->aws-smithy-types
smithy-xml
->aws-smithy-xml
- Rust
use
statement changes:smithy_async
->aws_smithy_async
smithy_client
->aws_smithy_client
smithy_eventstream
->aws_smithy_eventstream
smithy_http
->aws_smithy_http
smithy_http_tower
->aws_smithy_http_tower
smithy_json
->aws_smithy_json
smithy_protocol_test
->aws_smithy_protocol_test
smithy_query
->aws_smithy_query
smithy_types
->aws_smithy_types
smithy_xml
->aws_smithy_xml
- Cargo.toml changes:
New this week
- Moved the contents of
aws-auth
into theaws-http
runtime crate (smithy-rs#783) - Fix instances where docs were missing in generated services and add
#[warn_missing_docs]
(smithy-rs#779) - Add tracing output for resolved AWS endpoint (smithy-rs#784)
- Update AWS service models (smithy-rs#790)
- Add support for the following Glacier customizations:
- Set the ApiVersion header (smithy-rs#138, #787)