Rabbit MQ Pub/Sub Publish Metadata Propogation

[sethtomy]

Ask your question here

Hello!

I'm trying to use a headers exchange with Rabbit MQ but am not able to achieve it. I route my message from exchange to individual queues, by use case, using a particular header.

I could not get this working though DAPR even after setting this in the component:

    - name: publishMessagePropertiesToMetadata
      value: "true"

From the subscribing code it looks like the inverse of what I want is supported here.

I dug into the publishing code a bit and found this so it looks like this is intentional behavior?

So I guess that's my question, is this intentional behavior or is this propogation something I could request as a feature (and maybe contribute)?

[sethtomy]

This looks to be related to #6075

[lorenzoponsb]

I have the same problem but in my case I can't get the traceparent from the header

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[sethtomy]

Still hoping to get some input here to see what community thinks and to add support.