Skip to content

Break dependence on KafkaAutoConfiguration for Kinesis binder #183

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.

Sign up for GitHub

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

Jump to bottom
Closed
onobc opened this issue May 2, 2022 · 1 comment
Closed

Break dependence on KafkaAutoConfiguration for Kinesis binder #183

onobc opened this issue May 2, 2022 · 1 comment
Labels
enhancement

Comments

@onobc
Copy link

onobc commented May 2, 2022

Do the same thing to the Kinesis binder that was done for the other Kafka binders in spring-cloud/spring-cloud-stream#2362
@onobc onobc mentioned this issue May 2, 2022
Closed
@onobc onobc assigned onobc and unassigned onobc May 2, 2022
@artembilan artembilan transferred this issue from spring-cloud/spring-cloud-stream Jan 4, 2023
artembilan added a commit that referenced this issue Mar 24, 2023
@artembilan
GH-181, GH-182, GH-183: Migrate to AWS SDK v2
fba430a 
Fixes #181
Fixes #182
Fixes #183

* Upgrade to the latest dependencies
* Remove `SpringDynamoDBAdapterClient` since the DynamoDB Kinesis adapter
is not recommended by AWS per se.
* Fix docs to reflect new version logic
* Remove `@Import({ContextCredentialsAutoConfiguration.class, ContextRegionProviderAutoConfiguration.class})`
and fully rely on the auto-configuration
@artembilan
Copy link
Member

Fixed via: fba430a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@artembilan @onobc