-
Notifications
You must be signed in to change notification settings - Fork 73
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
Avoid queues auto creation #132
Comments
Hi Alexis, I would say the best way is to control it by the RabbitMQ user permissions. There you can define rules with regular expressions which queues/exchanges are allowed to create and access. This is how we control naming conventions and auto creation. This would only allow to create and access queues which are starting with "cfx", e.g. "cfx-machine1" and would not allow to auto create a queue called "machine1" BR |
Hi Michael, Thanks for your answer, this naming convention control is very interesting! But it doesn't resolve an issue we have with this scenario :
Do you or anyone has a solution for this? Best regards, Alexis |
Hi Alexis, as far as I know there is currently no other way beside the user permissions via RabbitMQ. Example: User: machine001 If you want to change the queue name for this machine you would remove permissions to QUEUE_001 first, delete QUEUE_001, add QUEUE_002 and grant permissions to QUEUE_002 to machine001. BR |
Hi Michael Thanks Michael, that's a pretty clever work around! Best regards, Alexis |
Hi every one,
When AddSubscribeChannel is called, with a queue that doesn't exist in the RabbitMQ broker, it is automatically created. Is there a way to avoid this behaviour and just send an exception instead ?
Thanks!
Alexis
The text was updated successfully, but these errors were encountered: