RabbitMQ: Specify how to populate messaging.destination.name

[joaopgrassi]

Fixes #1529

Changes

Specify in more detail how to populate messaging.destination.name for RabbitMQ. I based it on the Default exchange docs. My understanding is that a routing key is always present, even when using the default exchange (empty in this case). The routing key then is the queue name.

For all other cases, I left it as amq.default which is what RabbitMQ uses. I saw reference for it for example here: https://www.rabbitmq.com/docs/access-control

For convenience RabbitMQ maps AMQP 0-9-1's default exchange's blank name to 'amq.default' when performing permission checks.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• schema-next.yaml updated with changes to existing conventions.

[lmolkova]

maybe check if routing key and queue are the same and populate just one

[joaopgrassi]

Yeah I looked and it seems when receiving/delivering, only the routing key is present https://www.rabbitmq.com/docs/consumers#message-properties. Also, if I understand it right from some research, the routing key can be then also the same as queue name https://stackoverflow.com/questions/22655735/retrieve-name-of-rabbitmq-queue-where-message-was-consumed-from

So I think you're right, we should be good to keep only the exchange and routing key. PTAL 69b8141

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.