Closed mika closed 1 year ago
Gna sorry, I missed that new rabbitmqctl_list
as of 42d45ed1667 already checks for the according package version and uses --no-table-headers
as needed, we used an older version yet. Sorry for the noise and unneeded PR.
Thanks! Got it, yeah, thought I'd seen a PR for this, but hadn't come across it.
Thanks! Got it, yeah, thought I'd seen a PR for this, but hadn't come across it.
Yeah sorry, while looking into adding a test case I noticed that we were missing latest changes of puppet-rabbitmq, latest master works perfectly fine for both v3.7.8-4 and v3.8.2-1+deb10u1. :partying_face:
Incredibly fast reply from your side, kudos! Thanks and sorry again :)
rabbitmq-server's rabbitmqctl as of v3.7.8-4 (as shipped with Debian/buster) used to behave as follows:
As of rabbitmq-server v3.8.2-1+deb10u1 (as present in buster-security, see https://packages.qa.debian.org/r/rabbitmq-server/news/20230711T122021Z.html), it instead behaves as follows:
This results in:
There's a new
--no-table-headers
option available in more recent versions of RabbitMQ (which would also be available for rabbitmq-server v3.8.2-1+deb10u1), also see https://github.com/rabbitmq/rabbitmq-cli/issues/273.But since don't want to rely on having this option available (and therefore breaking compatibility with e.g. v3.7.8-4), let's instead skip lines matching this header output, to remaing both backwards as well as forwards compatible.
Related to https://github.com/voxpupuli/puppet-rabbitmq/issues/740
FTR: tested/verified with rabbitmq-server v3.7.8-4 + v3.8.2-1+deb10u1