You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I met an issue with the command to create queues. I have two vhosts in my application : / and /module. Then I made the configuration file with these two vhosts, here a sample :
Although leading slash is not required in the rabbitmq vhost name, many usage include it. So I ask why there is no url rewriting on every vhost name or is it intentional as the code seems to mean ?
Thanks for your great shared work.
The text was updated successfully, but these errors were encountered:
You don't need to put it in your configuration file nor in the command name (you can use directly module in your example).
Anyway, you're right, we could definitively transform / remove the leading slash when we found one. This will allow everyone to use either a slash, %2f or nothing. Of course, don't hesitate to create a PR if you want. :)
romainjanvier
added a commit
to romainjanvier/rabbit-mq-admin-toolkit
that referenced
this issue
Jun 21, 2018
I met an issue with the command to create queues. I have two vhosts in my application : / and /module. Then I made the configuration file with these two vhosts, here a sample :
I realized the command is not able to manage 2 vhosts in the same file (unfortunately...), anyway, I split this configuration into two files.
But the execution of the queues creation command with the vhost /module didn't work because of the leading slash. I was able to make work the command naming vhost
%2fmodule
. But there is no need to url rewrite the default vhost thanks to this code : https://github.com/odolbeau/rabbit-mq-admin-toolkit/blob/master/src/Bab/RabbitMq/VhostManager.php#L21Although leading slash is not required in the rabbitmq vhost name, many usage include it. So I ask why there is no url rewriting on every vhost name or is it intentional as the code seems to mean ?
Thanks for your great shared work.
The text was updated successfully, but these errors were encountered: