-
Notifications
You must be signed in to change notification settings - Fork 52
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
Fixing bug whereby a queue name with a slash in it resulted in a REST API error #144
Fixing bug whereby a queue name with a slash in it resulted in a REST API error #144
Conversation
CI is failing on unrelated issue which is being worked on in #139 @cognifloyd @odyssey4me @jgkirschbaum if anyone could take a quick look/review it would be appreciated. Thanks :) |
|
969f5b5
to
ef42923
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Im0 thanks for the bugfix!
one formatting thing from me
@csmart @odyssey4me @cognifloyd do you have any opinions on the patch?
Co-authored-by: Andrew Klychkov <[email protected]>
Thanks @Andersson007 ! Other rabbitmq_* modules had this issue previously and appear to also have been corrected with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Im0 SGTM, thanks! if no objections, i think it's OK if you merge it tomorrow
@Im0 so, as there are no objections, feel free to merge |
Thanks @Andersson007 |
@Im0 thanks for the contribution! |
SUMMARY
Fixes #114 - If a queue name was specified with a
/
in it, this resulted in a REST API error. Also, took the chance to add a documentation example for providingarguments
.ISSUE TYPE
COMPONENT NAME
rabbitmq_queue
ADDITIONAL INFORMATION