-
Notifications
You must be signed in to change notification settings - Fork 0
Extend dlq_* command line tools to work with RabbitMQ
#96
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
Conversation
…flag is set. Makes use of the rabbitmq management API
…h rabbitmq DLQ naming
… DLQ messages to in dlq_purge
…plifies dlq_check a little
Co-authored-by: Markus Gerstel <2102431+Anthchirp@users.noreply.github.com>
Co-authored-by: Markus Gerstel <2102431+Anthchirp@users.noreply.github.com>
Co-authored-by: Markus Gerstel <2102431+Anthchirp@users.noreply.github.com>
Co-authored-by: Markus Gerstel <2102431+Anthchirp@users.noreply.github.com>
Co-authored-by: Richard Gildea <rjgildea@users.noreply.github.com>
Co-authored-by: Richard Gildea <rjgildea@users.noreply.github.com>
Co-authored-by: Richard Gildea <rjgildea@users.noreply.github.com>
Co-authored-by: Richard Gildea <rjgildea@users.noreply.github.com>
|
I've tested these on the RabbitMQ live server and they work except that the I am |
Use the Zocalo site configuration throughout to remove the need for Diamond specific information. A new storage plugin will need to be added to the configuration to hold
zocalo.dlq.purge_locationwhere purged messages will be dumped.I think that all environments should work with the exception of a RabbitMQ test environment for
dlq_checkas it makes use of the RabbitMQ management API and the relevant credentials.Also add
dlq_checkfor RabbitMQ to IT health checks.