From dfbe4e0183600860aee3399c1fa81a9a208038de Mon Sep 17 00:00:00 2001 From: joshvanl Date: Fri, 22 Aug 2025 18:10:18 -0300 Subject: [PATCH] [1.16] RabbitMQ `publishMessagePropertiesToMetadata` Adds documentation for the new `publishMessagePropertiesToMetadata` rabbitmq pubsub component field. Signed-off-by: joshvanl --- .../supported-pubsub/setup-rabbitmq.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-rabbitmq.md b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-rabbitmq.md index 0f272f910..c3b4e69a8 100644 --- a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-rabbitmq.md +++ b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-rabbitmq.md @@ -66,6 +66,8 @@ spec: value: {podName} - name: heartBeat value: 10s + - name: publishMessagePropertiesToMetadata + value: "true" ``` {{% alert title="Warning" color="warning" %}} @@ -102,7 +104,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr | clientKey | Required for using TLS | TLS client key in PEM format. Must be used with `clientCert`. Can be `secretKeyRef` to use a secret reference. | `"-----BEGIN RSA PRIVATE KEY-----\n\n-----END RSA PRIVATE KEY-----"` | clientName | N | This RabbitMQ [client-provided connection name](https://www.rabbitmq.com/connections.html#client-provided-names) is a custom identifier. If set, the identifier is mentioned in RabbitMQ server log entries and management UI. Can be set to {uuid}, {podName}, or {appID}, which is replaced by Dapr runtime to the real value. | `"app1"`, `{uuid}`, `{podName}`, `{appID}` | heartBeat | N | Defines the heartbeat interval with the server, detecting the aliveness of the peer TCP connection with the RabbitMQ server. Defaults to `10s` . | `"10s"` - +| `publishMessagePropertiesToMetadata` | N | Whether to publish AMQP message properties (headers, message ID, etc.) to the metadata. | "true", "false" ## Communication using TLS @@ -475,6 +477,11 @@ spec: singleActiveConsumer: "true" ``` +## Publishing message properties to metadata + +To enable [message properties](https://www.rabbitmq.com/docs/publishers#message-properties) being published in the metadata, set the `publishMessagePropertiesToMetadata` field to `"true"` in the component spec. +This will include properties such as message ID, timestamp, and headers in the metadata of the published message. + ## Related links - [Basic schema for a Dapr component]({{% ref component-schema %}}) in the Related links section