Skip to content
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

SQS Multiple Gateways - One Queue using Message Group ID #592

Closed
phelinor opened this issue Apr 14, 2020 · 4 comments
Closed

SQS Multiple Gateways - One Queue using Message Group ID #592

phelinor opened this issue Apr 14, 2020 · 4 comments
Assignees

Comments

@phelinor
Copy link

Is your feature request related to a problem? Please describe.
I can't use 1 single SQS Queue for many different Argo SQS Gateways

Describe the solution you'd like
Would like "Message group ID" to be added to the Argo SQS Event Source to be able to feed many Argo SQS Gateways from 1 single SQS Queue

Describe alternatives you've considered

Additional context

@VaibhavPage VaibhavPage added the enhancement New feature or request label Apr 21, 2020
@VaibhavPage VaibhavPage added this to the v0.15.0 milestone Apr 21, 2020
@whynowy
Copy link
Member

whynowy commented Apr 22, 2020

Can you give more detail about your use case? To my understanding, SQS should not be used for multi consumers. @phelinor

@phelinor
Copy link
Author

phelinor commented Apr 23, 2020

Sure, basically we are using SQS Argo to create workflows that are sent from our Server to SQS but the development team has the Server installed in their local machines too along with Argo and Argo Events using Docker Desktop Kubernetes Feature so we would like to use one single SQS Queue instead of having to spinup a new one for every developer that's testing changes in their local machines. @whynowy

@phelinor
Copy link
Author

phelinor commented Apr 27, 2020

If support for multiple consumers is not desirable, what about support for https://github.com/localstack/localstack ?

@VaibhavPage VaibhavPage removed this from the v0.15.0 milestone May 1, 2020
@phelinor
Copy link
Author

Any updates on this by any chance?

@whynowy whynowy added wontfix and removed enhancement New feature or request needs investigation labels Mar 1, 2021
@whynowy whynowy closed this as completed Mar 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants