Our RabbitMQ admin code calls the rabbitmqadmin (v1) script directly. That script is no longer being maintained by RabbitMQ: https://www.rabbitmq.com/docs/management-cli#obtain-rabbitmqadmin-v1
I've had a lot of problems with rabbitmqadmin, especially with HTTPS connections and don't bother attempting to use it any more.
Since rabbitmqadmin is deprecated, and @robjarawan is finding issues with our current implementation (#1686, #1685, #1684), it might be worth re-writing eventually.
I think it would be best to write code that interacts with the RabbitMQ HTTP API directly. There's also rabbitmqadmin v2, which is written in Rust and distributed as a native binary. We could switch to that, but I think using the HTTP API is better because it doesn't depend on having a binary installed on the server running sr3 (which is frequently not also running RabbitMQ).
Our RabbitMQ admin code calls the
rabbitmqadmin(v1) script directly. That script is no longer being maintained by RabbitMQ: https://www.rabbitmq.com/docs/management-cli#obtain-rabbitmqadmin-v1I've had a lot of problems with
rabbitmqadmin, especially with HTTPS connections and don't bother attempting to use it any more.Since rabbitmqadmin is deprecated, and @robjarawan is finding issues with our current implementation (#1686, #1685, #1684), it might be worth re-writing eventually.
I think it would be best to write code that interacts with the RabbitMQ HTTP API directly. There's also
rabbitmqadminv2, which is written in Rust and distributed as a native binary. We could switch to that, but I think using the HTTP API is better because it doesn't depend on having a binary installed on the server running sr3 (which is frequently not also running RabbitMQ).