We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To help with #130 we should stop using 4 queues for messages, there isn't really any benefits to this beyond separating messages out.
Initially we should move support for 3 of the queues into the first queue handler, so that all 4 queues can still receive messages.
But eventually 3 of them will be removed. But we will need to follow up in Lagoon to change how messages are sent to remote to only use 1 queue.
The text was updated successfully, but these errors were encountered:
not sure but this might be related? #145
Sorry, something went wrong.
shreddedbacon
Successfully merging a pull request may close this issue.
To help with #130 we should stop using 4 queues for messages, there isn't really any benefits to this beyond separating messages out.
Initially we should move support for 3 of the queues into the first queue handler, so that all 4 queues can still receive messages.
But eventually 3 of them will be removed. But we will need to follow up in Lagoon to change how messages are sent to remote to only use 1 queue.
The text was updated successfully, but these errors were encountered: