[Issue] Fix for queue numeric argument conversion

[m2-assistant]

This issue is automatically created based on existing pull request: #26967: Fix for queue numeric argument conversion

---

Description (*)

Magento 2.4-develop

If we want to declare queue (I bet this also occurs the same way for exchanges) with arguments and we use numeric type argument in queue_topology.xml it is casted to string and in corrected file it gets wrapped in incorrect type for rabbit. Example of configuration:

 <exchange name="test.dead_letter" type="topic" connection="amqp">
        <binding id="test" topic="#" destinationType="queue"
                 destination="test_dead_letter">
            <arguments>
                <argument name="x-dead-letter-exchange" xsi:type="string">test.retry</argument>
                <argument name="x-message-ttl" xsi:type="number">36000</argument>
            </arguments>
        </binding>
    </exchange>

Of course using string type doesn't help as we get also string. While creating such a queue we get error similar to:
PRECONDITION_FAILED - inequivalent arg 'x-message-ttl'for queue 'test_dead_letter' in vhost '\': received the value '36000' of type 'longstr' but current is none.

If PR will be accepted, please port to 2.3 as well.

Related Pull Requests

This one has to be fixed first, as for now we are not able to declare queue with ANY parameters
#26966

Manual testing scenarios (*)

1. Declare queue with numeric argument, for example x-message-ttl
2. ...

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[magento-engcom-team]

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-38497 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #26967 by @bartoszkubicki in 2.4-develop branch
Related commit(s):

• d60cbb9ed28d4b307cd2b82721e0f19e501134b4
• 5e7d9f64168ecc50e9e9e4968ec1b8f3598a2cde
• 314ec92a7c82b70ac7460c21b2c82085e380d292
• 69eca0706fdfd74222b8a5aaab5a57bf0c4f0ea7
• 1fd701539fef71e05bdcfd7bcf5a09671482d199
• 7e97fb4b4c9c3b0ad6274272268f63055508cae1
• 8c8b9cf5220db0a8ffdc2ec16f1a092efcbe4fbd
• 0c6d2048ab3f162bdee85f1079b555fbf5f0f59e

The fix will be available with the upcoming 2.4.2 release.