[Bug] Message Queue Connection does not match Naming Conventions

[msyhr]

If a user follows the documentation here: https://devdocs.magento.com/guides/v2.4/config-guide/mq/manage-message-queues.html#start-message-queue-consumers to do the initial setup Rabbit MQ they instruct the user to use amqp as the connection name.

If that user then uses the PHP Storm plugin to scaffold a new message queue, this extension defines that connection name as ampq (p and q swapped).

This will cause the CLI and most likely other executions to fail.

This can be easily resolved by altering the connection names in either the generated .xml files or in your env.php, and I know (I think?) that the connection name is just an arbitrary string, but some others might run into the same issue I did and not realize it.

[m2-assistant]

Hi @msyhr. Thank you for your report.
To speed up processing of this issue, make sure that you provided sufficient information.

Add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[bohdan-harniuk]

Hello, @msyhr !

Thank you for your report!
We'll try to include fix in the upcoming release.

Thanks, Bohdan!

[bohdan-harniuk]

This issue successfully reproduced:

[bohdan-harniuk]

Hello, @msyhr!

This issue is fixed and will be delivered in the upcoming release: 4.2.2.

Thank you for your report!