Description
Describe the feature
For our use case, we have of downstream systems that are based on RabbitMQ and rely on message id and correlation id to be populated. Furthermore, messages from these systems might come to a dapr integrated application and the application would like to get these values.
Looking at https://www.rabbitmq.com/docs/publishers#message-properties, it's clear that there are many possible supported properties and headers. Dapr so far supports a few and we would love to expand on them.
It should be applied in the PubSub as well as in the Bindings for RabbitMQ and be added to outgoing messages.
Goal
RabbitMQ messages that are being sent from PubSub or Bindings need to have the Message ID and Correlation ID from the Cloud Event Message.
Release Note
RELEASE NOTE: ADD RabbitMQ message headers and properties are populated from the CloudEvent Message