Expose effective policy definition via CLI
Now it's only visible in the management UI. One can craft a series of calls to `rabbitmqctl list_queues` and `rabbitmqctl list_policies` to achieve similiar result. But it's more difficult, and also doesn't take operator policy (if any) into account.
This commit is contained in:
parent
e4c88a3d87
commit
398f072a03
|
@ -1321,7 +1321,11 @@ Whether the queue will be deleted automatically when no longer used.
|
|||
.It Cm arguments
|
||||
Queue arguments.
|
||||
.It Cm policy
|
||||
Effective policy name for the queue.
|
||||
Name of the user policy that is applied to the queue.
|
||||
.It Cm operator_policy
|
||||
Name of the operator policy that is applied to the queue.
|
||||
.It Cm effective_policy_definition
|
||||
Effective policy definition for the queue - merged values from the user and operator policies.
|
||||
.It Cm pid
|
||||
Erlang process identifier of the queue.
|
||||
.It Cm owner_pid
|
||||
|
|
|
@ -15,7 +15,8 @@ defmodule RabbitMQ.CLI.Ctl.Commands.ListQueuesCommand do
|
|||
|
||||
@default_timeout 60_000
|
||||
@info_keys ~w(name durable auto_delete
|
||||
arguments policy pid owner_pid exclusive exclusive_consumer_pid
|
||||
arguments policy operator_policy effective_policy_definition
|
||||
pid owner_pid exclusive exclusive_consumer_pid
|
||||
exclusive_consumer_tag messages_ready messages_unacknowledged messages
|
||||
messages_ready_ram messages_unacknowledged_ram messages_ram
|
||||
messages_persistent message_bytes message_bytes_ready
|
||||
|
|
Loading…
Reference in New Issue