-
-
Notifications
You must be signed in to change notification settings - Fork 329
AWS SDK v2 #20
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
Comments
Hey @driverpt, |
Alright then. Is there any branch I can create a PR on? |
The branch will be in this Github Repo, but there is no branch yet. We plan on revisiting some of the integrations in 3.x. so it won't be just an upgrade to sdk2. |
Is there someplace where we can view the status on 3.x? |
@MatejNedic how migration is going on? I see that no merges for 2 last months in branch v3. |
Hey @dmytrodanilenkov , |
@MatejNedic maybe you could point to small/minor issues I can start working on? Just to start get familiar with code base of project |
Hey folks, just checking in on this one. What's the roadmap/timeline expectations for releasing this? |
+1 - wanted feature |
+1 |
@MatejNedic anywhere we can view the status? |
@MatejNedic updates? |
Hopefully, things will start to move faster in 2022. Since in 3.0 we hope to rewrite SQS and SNS integration and potentially more. Currently, 3.0 is missing SQS, SNS, S3, Cognito, and RDS features. (ElastiCache is probably going to be removed). Sadly more answers than that I can't give at this time. |
Is there any PR with ongoing work on those components? |
Yes. But are there any created Issues/PRs/Milestones to track? |
There is a Milestone for 3.0.x https://github.com/awspring/spring-cloud-aws/milestone/4 . |
Is there any expected due date for the new version? |
I believe the CloudWatch integration will need to be updated as well. Is that on the plan? Thanks! |
Any news? |
I currently see that there any no commits in this repository. Any reason? @MatejNedic Explantations would be very helpful since this is a very anticipated issue. |
Anybody here ?! |
Seems like the migration of Spring Cloud AWS into AWS people was much less successful than the migration of Spring Cloud Azure\ GCP to their people. This project is just unmaintained, while there are lots of people waiting for these features. The no answers policy is irresponsible and immature. |
@migroskub so sorry about this. There is a difference with the projects you mentioned, those are maintained by big companies. In this case, the project depends on some volunteers which dedicate their free time to the project which is not only working on the project itself but also experiment such this case which the idea to use aws sdk v2 is to enable and create native images. |
@MatejNedic need any more help? If the migration effrot is broken into part it would be easier to contribute? |
Continuing discussion from #224, I think we should split I'm already working on migrating Spring Cloud AWS Messaging to the new |
@MazizEsa we are planning to finish a roadmap for 3.0 with issues soon. Need to consult with @maciejwalkowiak and @eddumelendez . Currently, we are working on closing existing PR's and releasing 2.3.4 and 2.4.0. |
Integrations already migrated that are going to be released in Spring Cloud AWS 3.0 M1
Which leaves us few more to be ported from 2.x in further milestones:
Closing this issue, as it's too wide. Look into specific integration issues/PRs to track progress. |
Uh oh!
There was an error while loading. Please reload this page.
Type: Feature
Is Spring Cloud AWS 3.x going to use AWS SDK v2 exclusively ?
The text was updated successfully, but these errors were encountered: