v2.15.0

v2.15.0 (Sep 30, 2025)

Enhancements

• permissions is a new command group for operations on user permissions:

  rabbitmqadmin permissions list
  
  rabbitmqadmin permissions declare --user "user1" --configure ".*" --read ".*" --write ".*"
  
  rabbitmqadmin permissions delete --user "user1"

• user_limits is a new command group for operations on per-user limits:

  rabbitmqadmin user_limits list
  
  rabbitmqadmin user_limits declare --user "user1" --name "max-connections" --value "100"
  
  rabbitmqadmin user_limits delete --user "user1" --name "max-connections"

• vhost_limits is a new command group for operations on virtual host limits:

  rabbitmqadmin vhost_limits list
  
  rabbitmqadmin vhost_limits declare --name "max-connections" --value "1000"
  
  rabbitmqadmin vhost_limits delete --name "max-connections"

Deprecations

• "Verb" command groups (list [object], declare [object], delete [object]) are now deprecated in favor of the "noun" group commands (such as users [operation] or permissions [operation]).

v2.14.0

v2.14.0 (Sep 30, 2025)

Enhancements

• Several commands now have minimalistic progress indicators: federation disable_tls_peer_verification_for_all_upstreams, federation enable_tls_peer_verification_for_all_upstreams, shovels disable_tls_peer_verification_for_all_source_uris, shovels disable_tls_peer_verification_for_all_destination_uris, shovels enable_tls_peer_verification_for_all_source_uris, and shovels enable_tls_peer_verification_for_all_destination_uris

• vhosts delete_multiple is a new command that deletes multiple virtual hosts matching a regular expression pattern:

  # Delete all virtual hosts matching a pattern (requires explicit approval)
  rabbitmqadmin vhosts delete_multiple --name-pattern "test-.*" --approve
  
  # Dry-run to see what would be deleted without actually deleting
  rabbitmqadmin vhosts delete_multiple --name-pattern "staging-.*" --dry-run
  
  # Non-interactive mode (no --approve flag needed)
  rabbitmqadmin --non-interactive vhosts delete_multiple --name-pattern "temp-.*"

  One virtual host — named /, that is, the default one — is always skipped to preserve
  at least one functional virtual host at all times.

  Important: this command is very destructive and should be used with caution. Always test with --dry-run first.

• vhosts enable_deletion_protection and vhosts disable_deletion_protection are two new commands
  for managing virtual host deletion protection:

  # Enable deletion protection for a virtual host
  rabbitmqadmin vhosts enable_deletion_protection --name "production-vhost"
  
  # Disable deletion protection for a virtual host
  rabbitmqadmin vhosts disable_deletion_protection --name "production-vhost"

  Protected virtual hosts cannot be deleted, either individually using vhosts delete or
  as part of bulk operations using vhosts delete_multiple. To delete a protected
  virtual host, its protection must be lifted first.

v2.13.0

v2.13.0 (Sep 26, 2025)

Enhancements

• Memory breakdown commands (show memory_breakdown_in_bytes and show memory_breakdown_in_percent) now gracefully handle
  cases where memory breakdown stats are not yet available on the target node

• shovel enable_tls_peer_verification_for_all_source_uris is a new command that enables TLS peer verification
  for all shovel source URIs:

  # The certificate and private key paths below refer
  # to the files deployed to the target RabbitMQ node(s), not to the
  # local files.
  #
  # As such, these arguments are command-specific and should not be confused
  # with the global `--tls-ca-cert-file`, `--tls-cert-file`, and `--tls-key-file`
  # arguments that are used by `rabbitmqadmin` itself to connect to the target node
  # over the HTTP API.
  rabbitmqadmin shovels enable_tls_peer_verification_for_all_source_uris \
      --node-local-ca-certificate-bundle-path /path/to/node/local/ca_bundle.pem \
      --node-local-client-certificate-file-path /path/to/node/local/client_certificate.pem \
      --node-local-client-private-key-file-path /path/to/node/local/client_private_key.pem

  See TLS guide and Shovel guide to learn more.

• shovel enable_tls_peer_verification_for_all_destination_uris is a new command that enables TLS peer verification
  for all shovel destination URIs:

  # Ditto, the certificate and private key paths below refer
  # to the files deployed to the target RabbitMQ node(s), not to the
  # local files.
  rabbitmqadmin shovels enable_tls_peer_verification_for_all_destination_uris \
      --node-local-ca-certificate-bundle-path /path/to/node/local/ca_bundle.pem \
      --node-local-client-certificate-file-path /path/to/node/local/client_certificate.pem \
      --node-local-client-private-key-file-path /path/to/node/local/client_private_key.pem

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.59.0

v2.12.0

v2.12.0 (Sep 23, 2025)

Enhancements

• federation enable_tls_peer_verification_for_all_upstreams is a new command that enables TLS peer verification
  for all federation upstreams:

  # Note that the certificate and private key paths below refer
  # to the files deployed to the target RabbitMQ node(s), not to the
  # local files.
  #
  # As such, these arguments are command-specific and should not be confused
  # with the global `--tls-ca-cert-file`, `--tls-cert-file`, and `--tls-key-file`
  # arguments that are used by `rabbitmqadmin` itself to connect to the target node
  # over the HTTP API.
  rabbitmqadmin federation enable_tls_peer_verification_for_all_upstreams \
      --node-local-ca-certificate-bundle-path /path/to/node/local/ca_bundle.pem \
      --node-local-client-certificate-file-path /path/to/node/local/client_certificate.pem \
      --node-local-client-private-key-file-path /path/to/node/local/client_private_key.pem

  See TLS guide and Federation guide to learn more.

• shovel disable_tls_peer_verification_for_all_source_uris is a new command that disables TLS peer verification
  for all shovel source URIs.

  Important: this command should only be used to undo incorrect shovel source URIs, after a bad deployment, for example,
  if peer verification was enabled before certificates and keys were
  deployed.

• shovel disable_tls_peer_verification_for_all_source_uris is a new command that disables TLS peer verification
  for all shovel source URIs.

  Important: this command should only be used to undo incorrect shovel destination URIs (see above).

• All delete_* and clear_* commands now support the --idempotently flag (previously it was just a few):

  • bindings delete
  • close connection
  • close user_connections
  • connections close
  • connections close_of_user
  • exchanges delete
  • exchanges unbind
  • federation delete_upstream
  • global_parameters clear
  • operator_policies delete
  • parameters clear
  • policies delete
  • queues delete
  • shovels delete
  • streams delete
  • users delete
  • vhosts delete

v2.11.0

v2.11.0 (Sep 22, 2025)

Enhancements

• federation disable_tls_peer_verification_for_all_upstreams is a new command that disables TLS peer verification
  for all federation upstreams.

  Important: this command should only be used in case of an emergency, for example,
  if peer verification was enabled prematurely during
  a deployment and all federation links fail to connect.

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.57.0

v2.10.0

v2.10.0 (Sep 18, 2025)

Enhancements

• definitions export_from_vhost now supports --transformations:

  # previously only 'definitions export' supported --transformations
  rabbitmqadmin --vhost "my-vhost" definitions export_from_vhost \
                --transformations prepare_for_quorum_queue_migration,drop_empty_policies \
                --file "my-vhost.definitions.json"

Bug Fixes

• The prepare_for_quorum_queue_migration transformation did not remove CMQ-related keys
  such as x-ha-mode from optional queue arguments

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.52.0

v2.9.0

v2.9.0 (Aug 25, 2025)

Enhancements

• RabbitMQ 4.2 forward compatibility: shovels list_all and shovels list now can render
  local shovel rows

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.44.0

v2.8.2

v2.8.2 (Aug 19, 2025)

Enhancements

• definitions export is now compatible with RabbitMQ 3.10.0, a series that has reached end of life (EOL) in late 2023

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.43.0

v2.8.1

v2.8.1 (Aug 14, 2025)

Bug Fixes

• shovels list and shovels list_all panicked when target cluster had at least one
  static shovel

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.42.0

v2.8.0

v2.8.0 (Aug 11, 2025)

Bug Fixes

• shovels list_all panicked when one of the shovels was in the terminated state

Enhancements

• shovels list is a new command that lists shovels in a particular virtual host

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.41.0