f23f3276c4
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 <arnaud.morin@ovhcloud.com> Change-Id: I34bad0f6d8ace475c48839adc68a023dd0c380de
12 lines
451 B
YAML
12 lines
451 B
YAML
---
|
|
features:
|
|
- |
|
|
Allow creation of transient queues with no expire.
|
|
When an operator rely on rabbitmq policies, there is no point to set the
|
|
queue TTL in config.
|
|
When the rabbit_transient_queues_ttl is set to 0, no x-expire parameter
|
|
will be set on queue declaration.
|
|
In that specific situation, it is recommended to set an expire value using
|
|
rabbitmq policies.
|
|
See https://www.rabbitmq.com/parameters.html#policies
|