-
-
Notifications
You must be signed in to change notification settings - Fork 498
Correctly handle rabbitmqctl list_users output #1060
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
The rabbitmq_user provider seemed broken to me, at least with a recent version of rabbitmq (I'm talking about 4.0.5 in Debian 13 aka Trixie). This small patch fixes the provider.
https://github.com/voxpupuli/puppet-rabbitmq?tab=readme-ov-file#module-description The module has been tested against 3.6, and has some minor fixes for later versions IIRC. I doubt it's been tested with 4.x, and does not currently have any active maintainers. I would personally like to see something like #926, combined with dropping support for older versions, and making sure we're acceptance testing with a recent RMQ version, before we get too deep into supporting 4.x at all. (Once older version support is dropped, most of the providers could also use the json flag for the CLI, which would resolve a lot of the parsing issues that exist now). We can happily look at small fixes that improve compatibility with newer versions of RMQ, but for sure we'd need additional spec tests added for how the new output looks. It might also make some more sense to key on the version, for example, like this:
or like this: puppet-rabbitmq/lib/puppet/provider/rabbitmq_vhost/rabbitmqctl.rb Lines 19 to 42 in 5216e37
I would worry that even if you fix this issue, you may turn up other issues. |
Hi. Well, I'm using this module in production under Debian 13 (aka: Trixie) with the patch I just sent plus a bit more (like puppetserver 8.4.0 support, ie: fixes to stop using toplevel facts that are now gone). Full list of patches here: I can do the work to add all of my patches, but if you start refusing them it's going to be complicated... As for the validation tests, I'm not sure how to fix them. |
There's no intent to gatekeep here, and we'll be very happy to accept contributions, but do note that Vox may request that unit tests be added. In this case, we also only unit test on a single version (an old version) of rabbitmq, so unless / until someone takes over more active maintenance of this module, having confident that changes are safe and avoid regressions is particularly important. These links may be of some help in terms of how to make changes, how to run some of these tests and style checks locally, etc.:
These are rubocop errors. Some can be autofixed with
|
The rabbitmq_user provider seemed broken to me, at least with a recent version of rabbitmq (I'm talking about 4.0.5 in Debian 13 aka Trixie).
This small patch fixes the provider.