Debian Codegraph @

debian/patches/

7 patches in series

  1. do-not-download-rabbitmqadmin-in-debian.patch
    Author
    Thomas Goirand <[email protected]>
    Forwarded
    no
    Last update
    2019-04-08
  2. correctly-report-rabbitmq-version.patch
    The output of "rabbitmqctl -q status" has changed between Buster and Bullseye, confusing this puppet module. This fixes the problem. As the version is now correctly detected, this puppet module can now correctly use the --no-table-headers parameters for querying Rabbit.
    Author
    Thomas Goirand <[email protected]>
    Forwarded
    https://github.com/voxpupuli/puppet-rabbitmq/pull/872
    Last update
    2021-03-10
  3. add-minus-q-when-calling-rabbitmq-plugin-list.patch
    The -q is needed in the Bullseye version to avoid the hearder.
    Author
    Thomas Goirand <[email protected]>
    Forwarded
    no
    Last update
    2021-01-21
  4. increase-rabbitmq-timeout.patch
    The new version of rabbitmq is taking much longer to reply, which often goes below the timeout of 10 seconds, resulting in the rabbitmq puppet providers to just fail. Increasing to 20 seconds just fixes it for me.
    Author
    Thomas Goirand <[email protected]>
    Forwarded
    no
    Last update
    2021-01-21
  5. trixie-support.patch
    Author
    Thomas Goirand <[email protected]>
    Forwarded
    no
    Last update
    2025-05-27
  6. fix-list_users-provider.patch
    Author
    Thomas Goirand <[email protected]>
    Forwarded
    https://github.com/voxpupuli/puppet-rabbitmq/pull/1060
    Last update
    2025-05-29
  7. setup-all-nodes-as-disk-nodes.patch
    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 <[email protected]>
    Forwarded
    no
    Last update
    2025-08-11
dir..
file add-minus-q-when-calling-rabbitmq-plugin-list.patch
file correctly-report-rabbitmq-version.patch
file do-not-download-rabbitmqadmin-in-debian.patch
file fix-list_users-provider.patch
file increase-rabbitmq-timeout.patch
file series
file setup-all-nodes-as-disk-nodes.patch
file trixie-support.patch