feat(streaming): add AWS Kinesis streaming provider - #8967
Conversation
|
this is what I've been waiting for. thanks :) |
30ea2c9 to
be54597
Compare
|
CI build failing due to missing package even though the package can be selected from that feed locally.
|
@ReubenBond |
|
Just wanted to check in and see if there’s been any progress on this. It’s something I’ve been hoping to have for a while. |
be54597 to
60e3a69
Compare
|
I can see some recent activity on this PR, I'm currently using SQS, and a custom PR for SQS FIFO. If someone is able to provide a list of outstanding tasks on this PR, I can provide resource to get this over the line. |
|
Has this been parked? For my project Kinesis integration would be very useful |
9987089 to
7450710
Compare
8363494 to
2c62e19
Compare
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3f5060d4-b229-476c-bdf3-9923ad459bb2
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3f5060d4-b229-476c-bdf3-9923ad459bb2
1a4f74d to
e1dc692
Compare
Relates to #8966
Adds a persistent stream provider for AWS Kinesis using the AWS .NET SDK directly, without requiring the JVM-based Kinesis Client Library. The provider includes client and silo configuration, shard discovery and topology monitoring, durable iterator recovery, provider-correlated tests, and Ministack-backed CI coverage.
This PR is organized as two commits: the exact grain-backed checkpointer commit reviewed in #10345, followed by the Kinesis provider commit. The PRs cannot form a native GitHub stack because their head branches live in different forks.