-
Notifications
You must be signed in to change notification settings - Fork 161
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
draft: WIP SQS integration. #918
base: main
Are you sure you want to change the base?
Conversation
I have to polish stable Redis release. Then, we can start to work on this on. |
Hello there! Sorry for waiting so long: I had to refactore project structure to unblock future featrues. Now we are ready to add a new broker support: are you still interested to help me with it? |
Hey, I just wanted to check in on this. I have a use case I need the SQS broker for and potentially some time to contribute to its completion, but I don't want to duplicate work if anyone else is currently working on it. |
@ccastleberry thank you for the suggestion, but I freeze all new brokers support until inner structure stabilize. Can we wait for 0.6.0 release (I am planning to make all breaking changes in it) and come back to SQS then? |
Sure, any estimate on when you expect that to get 0.6.0 released? I don't want to use propan since it's deprecated in favor of fast stream and I'd rather spend my time contributing than building an in house solution for sqs. |
October, I hope. I am planning to focus on 0.6.0 now and release it as soon as possible. Then we can add a new broker support in a few days. |
Oh wow. Thanks for the info. I look forward to it! |
Description
SQS integration for sub/pub message/s.
Fixes #794
Type of change
Checklist
scripts/lint.sh
shows no errors)scripts/test-cov.sh
scripts/static-anaylysis.sh