Description: Setup all nodes as disk nodes
 In most production setups, it is advised to set all nodes as disk nodes
 bacause of:
  * Simplicity – all nodes behave the same; no special recovery procedures.
  * Resilience – if one disk node fails, you don’t risk being left with
    only RAM nodes (which could cause data loss if all RAM nodes restart).
  * Operational flexibility – you can remove or add nodes without worrying
    about “last disk node” constraints.
  * Modern RabbitMQ performance – RAM nodes used to help in early versions
    (pre-3.x) when Mnesia disk I/O was slow, but with current disk and SSD
    speeds, the performance difference is often negligible.
Author: Thomas Goirand <zigo@debian.org>
Forwarded: no
Last-Update: 2025-08-11

--- puppet-module-puppetlabs-rabbitmq-8.5.0.orig/templates/rabbitmq.config.erb
+++ puppet-module-puppetlabs-rabbitmq-8.5.0/templates/rabbitmq.config.erb
@@ -16,6 +16,7 @@
 <% end -%>
 <% if @config_cluster -%>
     {cluster_nodes, {[<%= @cluster_nodes.map { |n| "\'rabbit@#{n}\'" }.join(', ') %>], <%= @cluster_node_type %>}},
+    {rabbit, [{disk_nodes, [<%= @cluster_nodes.map { |n| "\'rabbit@#{n}\'" }.join(', ') %>]}]},
     {cluster_partition_handling, <%= @cluster_partition_handling %>},
 <% end -%>
     {tcp_listen_options, [