Skip to content
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

Add unmaintained rusoto_credential #1494

Merged
merged 1 commit into from
Dec 18, 2022

Conversation

iliana
Copy link
Contributor

@iliana iliana commented Dec 16, 2022

Hi. I'm ostensibly one of the maintainers of Rusoto, here to report its lack of maintenance.

Rusoto has been deprecated for a while; this is a more formalized notice of such to help churn downstream automation to make it clear that users need to migrate to aws-sdk-rust.

This is a somewhat unique case for the RustSec advisory DB, I think. The Rusoto project is made up of a little over 200 separate crates, but every crate in the tree either is or depends on rusoto_credential. Most users don't directly depend on rusoto_credential though, so I feel that listing an advisory for only that crate is a bit confusing, but hopefully downstream systems show the full description for context.

Rusoto has been deprecated for a while; this is a more formalized notice
of such. `rusoto_credential` is the most fundamental crate in the tree.
@pinkforest
Copy link
Contributor

Thanks a lot for rusoto - it was good as long as it lasted ❤️

And thanks for contribution and keeping everyone up-to-date -

And yup lightning up the common crate is the way we've gone :)

@pinkforest pinkforest merged commit 7cf8350 into rustsec:main Dec 18, 2022
@kennethuil
Copy link

aws_sdk_rust still has this note in its repo:

Please Note: The SDK is currently released as a developer preview and is intended strictly for feedback purposes only. Do not use this SDK for production workloads.

So that leaves us with no recommended way to use AWS APIs in production?

@iliana
Copy link
Contributor Author

iliana commented Apr 6, 2023

That's a good question for AWS. I'm not sure they'd recommend you use a community-maintained SDK in production regardless of maintenance status, either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants