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

v2.7.2

v2.7.2 (Aug 6, 2025)

Bug Fixes

• shovels declare_amqp091 panicked when the --source-exchange argument was not provided,
  even if --source-queue was

v2.7.1

v2.7.1 (in development)

Bug Fixes

• Improved handling of missing or impossible to load/parse --tls-ca-cert-file on the command line.

  The tool now properly handles cases where a CA certificate file path is not provided, making
  CA certificate loading optional rather than required, which prevents crashes when TLS is used
  without a custom CA certificate bundle

• show overview could panic when run against a freshly booted RabbitMQ node that did not have certain
  metrics/rates initialized and available. Now those metrics will use the default values for their types,
  such as 0 and 0.0 for the counters, gauges, rates

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.40.0

v2.7.0

v2.7.0 (Jul 15, 2025)

Enhancements

• rabbitmqadmin.conf now supports more TLS-related settings: ca_certificate_bundle_path (corresponds to --tls-ca-cert-file on the command line),
  client_certificate_file_path (corresponds to --tls-cert-file), and client_private_key_file_path (corresponds to --tls-key-file).

  As the names suggest, they are used to configure the CA certificate bundle file path, the client certificate file path,
  and the client private key file path, respectively:

   [production]
   hostname = "(redacted)"
   port = 15671
   username = "user-efe1f4d763f6"
   password = "(redacted)"
   tls = true
   ca_certificate_bundle_path = "/path/to/ca_certificate.pem"
   client_certificate_file_path = "/path/to/client_certificate.pem"
   client_private_key_file_path = "/path/to/client_key.pem"

  To learn more, see RabbitMQ's TLS guide.

Bug Fixes

• Tool version was unintentionally missing from -h output (but present in its long counterpart, --help)
• The tls setting in rabbitmqadmin.conf, a --use-tls equivalent, was not respected when connecting to a node
  in certain cases

v2.6.0

v2.6.0 (Jul 12, 2025)

Enhancements

• New command, passwords salt_and_hash, that implements the password salting and hashing algorithm
  used by RabbitMQ's internal authentication backend:

  rabbitmqadmin passwords salt_and_hash "sEkr37^va1ue"
  # => ┌───────────────┬──────────────────────────────────────────────────┐
  # => │ Result                                                           │
  # => ├───────────────┼──────────────────────────────────────────────────┤
  # => │ key           │ value                                            │
  # => ├───────────────┼──────────────────────────────────────────────────┤
  # => │ password hash │ vRZC0bF0Ut4+6pmcQRSu87S/wRXdHRalgY5DV/5KDd5SzK69 │
  # => └───────────────┴──────────────────────────────────────────────────┘

  This value can be passed as a --password-hash when creating a user with the users declare
  command.

• users declare now supports a new argument, --hashing-algorithm, that accepts two
  possible values: sha256 (the default) and sha512:

  # RabbitMQ nodes must also be configured to use SHA-512 password hashing,
  # or this user won't be able to authenticate against them
  rabbitmqadmin users declare --username "username43742" --password "example_%^4@8s7" --hashing-algorithm "sha512"

  Target RabbitMQ nodes must be configured to use the same hashing algorithm (SHA-256 is
  used by default).

v2.5.0

v2.5.0 (Jul 11, 2025)

Enhancements

• definitions export now supports a new transformation: prepare_for_quorum_queue_migration.

  rabbitmqadmin definitions export --transformations prepare_for_quorum_queue_migration,drop_empty_policies --stdout

  This one not only strips off the CMQ-related keys
  but also handles an incompatible "overflow"/"x-overflow" key value
  and "queue-mode"/"x-queue-mode" keys, both not supported
  by quorum queues.

Bug Fixes

• export definitions CLI interface was unintentionally different from that of definitions export.
  Note that export definitions only exists for better backwards compatibility with rabbitmqadmin v1,
  use definitions export when possible.