-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
migration guide for aws-smithy-client #952
Comments
What is the open source project trying to do with the client? Could you share a link to it? We have a lot of migration guides at the moment but I think this one is the most relevant. |
The changelogs for both aws-sdk-rust and smithy-rs should have information on breaking changes: |
The example code also needs to be updated. It is currently broken with this change. |
Thanks for letting us know! It looks like it fell out of the Cargo workspace, so it wasn't getting picked up by CI. I filed an issue on the examples repo to fix it: awsdocs/aws-doc-sdk-examples#5668 |
The project is vector, there are usages such as this throughout the codebase: https://github.com/vectordotdev/vector/blob/master/src/sinks/aws_cloudwatch_logs/config.rs#L36-L50 I'll read through the provided docs and give it a crack at some point |
Please checkout the changelogs, or let us know if you have any other specific migration questions
|
Comments on closed issues are hard for our team to see. |
Describe the issue
I'm updating some dependencies for an open-source project and they are using aws-smithy-client.
When I browse the docs for this crate, it shows that the crate is now empty and was deprecated some time ago.
However, I cannot find a corresponding guide for migrating away from using this crate.
Can someone point me to such documentation, or an example of how to use some alternative in place of the now-removed crate?
Links
https://docs.rs/aws-smithy-client/latest/aws_smithy_client/
The text was updated successfully, but these errors were encountered: