-
Notifications
You must be signed in to change notification settings - Fork 196
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
Subscribing queues to topics #6032
Comments
@eladb it seems pretty straightforward, can you elaborate why you added the needs-discussion label? |
It was automatically added |
Guys, this is basically what I did in messagefanout https://github.com/winglang/winglibs/tree/main/messagefanout
|
Very cool @marciocadev - based on feedback from users we see this as something that can be incorporated into the standard library. Would you like to work on this? |
Yes, I can do it |
I started implementing in the simulator, which is always the hardest part for me, but I think visually it turned out pretty cool.
|
Now I see, I will change to |
- [x] subscribing queue to topic (sim) - [x] subscribing queue to topic (tf-aws) - [x] subscribing queue to topic (awscdk) - [x] wing test Closes #6032 ## Checklist - [x] Title matches [Winglang's style guide](https://www.winglang.io/contributing/start-here/pull_requests#how-are-pull-request-titles-formatted) - [x] Description explains motivation and solution - [ ] Tests added (always) - [ ] Docs updated (only required for features) - [ ] Added `pr/e2e-full` label if this feature requires end-to-end testing *By submitting this pull request, I confirm that my contribution is made under the terms of the [Wing Cloud Contribution License](https://github.com/winglang/wing/blob/main/CONTRIBUTION_LICENSE.md)*.
Congrats! 🚀 This was released in Wing 0.67.12. |
Use Case
I'd like to be able to have send notifications sent to a
cloud.Topic
into acloud.Queue
for processing.Proposed Solution
Something like this:
Implementation Notes
In AWS, it is possible to connect SNS to SQS directly.
Component
No response
Community Notes
The text was updated successfully, but these errors were encountered: