Closed as not planned
Description
Describe the feature
For our use case, we have a lot of downstream systems that are based on RabbitMQ and rely on message id and correlation id to be populated. These properties should be in the Cloud Event Message.
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.
Unclear
- It's not clear to me, how e.g. the CloudEvent properties will be available in the PublishRequest type.
- maybe it would be beneficial if the metadata of the PublishRequest can be used to set any kind of header or property in the AMQP message, so that it also works in situation, where the downstream AMQP brokers expect certain properties to be set.
Release Note
RELEASE NOTE: ADD RabbitMQ message headers and properties are populated from the CloudEvent Message