When an operator rely on rabbitmq policies, there is no point to set the
queue TTL in config.
Moreover, using policies is much more simpler as you dont need to
delete/recreate the queues to apply the new parameter (see [1]).
So, adding the possibility to set the transient queue TTL to 0 will
allow the creation of the queue without the x-expire parameter and only
the policy will apply.
Reviewed: https:/ /review. opendev. org/c/openstack /oslo.messaging /+/889701 /opendev. org/openstack/ oslo.messaging/ commit/ f23f3276c4f8c15 6c7a917ffd05db6 b3b010b807
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit f23f3276c4f8c15 6c7a917ffd05db6 b3b010b807
Author: Arnaud Morin <email address hidden>
Date: Wed Jul 26 12:12:16 2023 +0200
Allow creating transient queues with no expire
When an operator rely on rabbitmq policies, there is no point to set the
queue TTL in config.
Moreover, using policies is much more simpler as you dont need to
delete/recreate the queues to apply the new parameter (see [1]).
So, adding the possibility to set the transient queue TTL to 0 will
allow the creation of the queue without the x-expire parameter and only
the policy will apply.
[1] https:/ /www.rabbitmq. com/parameters. html#policies
Related-bug: #2031497
Signed-off-by: Arnaud Morin <email address hidden> 75c48839adc68a0 23dd0c380de
Change-Id: I34bad0f6d8ace4