From d5754ca63eeddd3d3f04997de84bf3c9238a8f58 Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Mon, 26 Jun 2023 17:15:21 -0400 Subject: [PATCH 1/4] add note Signed-off-by: Hannah Hunter --- .../components-reference/supported-bindings/rabbitmq.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/rabbitmq.md b/daprdocs/content/en/reference/components-reference/supported-bindings/rabbitmq.md index 89d150f43..d3ea62da3 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/rabbitmq.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/rabbitmq.md @@ -57,6 +57,8 @@ The above example uses secrets as plain strings. It is recommended to use a secr ## Spec metadata fields +> When a new RabbitMQ message gets published, all values from the associated metadata will be added to the message's header values. + | Field | Required | Binding support | Details | Example | |--------------------|:--------:|------------|-----|---------| | queueName | Y | Input/Output | The RabbitMQ queue name | `"myqueue"` | @@ -73,6 +75,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr | caCert | N | Input/Output | The CA certificate to use for TLS connection. Defaults to `null`. | `"-----BEGIN CERTIFICATE-----\nMI..."` | | clientCert | N | Input/Output | The client certificate to use for TLS connection. Defaults to `null`. | `"-----BEGIN CERTIFICATE-----\nMI..."` | | clientKey | N | Input/Output | The client key to use for TLS connection. Defaults to `null`. | `"-----BEGIN PRIVATE KEY-----\nMI..."` | + ## Binding support This component supports both **input and output** binding interfaces. From 40813a1f9c5ee616bf9c819cd00df26f9ebe7582 Mon Sep 17 00:00:00 2001 From: Mark Fussell Date: Fri, 30 Jun 2023 15:32:49 -0700 Subject: [PATCH 2/4] Update daprdocs/content/en/reference/components-reference/supported-bindings/rabbitmq.md Signed-off-by: Mark Fussell --- .../components-reference/supported-bindings/rabbitmq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/rabbitmq.md b/daprdocs/content/en/reference/components-reference/supported-bindings/rabbitmq.md index d3ea62da3..30b5b1029 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/rabbitmq.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/rabbitmq.md @@ -57,7 +57,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr ## Spec metadata fields -> When a new RabbitMQ message gets published, all values from the associated metadata will be added to the message's header values. +> When a new RabbitMQ message gets published, all values from the associated metadata are added to the message's header values. | Field | Required | Binding support | Details | Example | |--------------------|:--------:|------------|-----|---------| From f88b1d998edffec1cd190a7503f8e8328cf3cd47 Mon Sep 17 00:00:00 2001 From: guergabo <65991626+guergabo@users.noreply.github.com> Date: Mon, 3 Jul 2023 14:14:14 -0500 Subject: [PATCH 3/4] fix(type): pubsub.aws.snssqs not pubsub.snssqs (#3594) Signed-off-by: guergabo --- .../supported-pubsub/setup-aws-snssqs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-aws-snssqs.md b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-aws-snssqs.md index c5a9e5c73..4ddddb3a1 100644 --- a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-aws-snssqs.md +++ b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-aws-snssqs.md @@ -9,7 +9,7 @@ aliases: ## Component format -To set up AWS SNS/SQS pub/sub, create a component of type `pubsub.snssqs`. See the [pub/sub broker component file]({{< ref setup-pubsub.md >}}) to learn how ConsumerID is automatically generated. Read the [How-to: Publish and Subscribe guide]({{< ref "howto-publish-subscribe.md#step-1-setup-the-pubsub-component" >}}) on how to create and apply a pub/sub configuration. +To set up AWS SNS/SQS pub/sub, create a component of type `pubsub.aws.snssqs`. See the [pub/sub broker component file]({{< ref setup-pubsub.md >}}) to learn how ConsumerID is automatically generated. Read the [How-to: Publish and Subscribe guide]({{< ref "howto-publish-subscribe.md#step-1-setup-the-pubsub-component" >}}) on how to create and apply a pub/sub configuration. ```yaml @@ -18,7 +18,7 @@ kind: Component metadata: name: snssqs-pubsub spec: - type: pubsub.snssqs + type: pubsub.aws.snssqs version: v1 metadata: - name: accessKey @@ -147,7 +147,7 @@ kind: Component metadata: name: snssqs-pubsub spec: - type: pubsub.snssqs + type: pubsub.aws.snssqs version: v1 metadata: - name: accessKey From bcde4f0ef10dcea60938d1ac42cd03342482d28a Mon Sep 17 00:00:00 2001 From: jjkcharles <1765598+jjkcharles@users.noreply.github.com> Date: Mon, 3 Jul 2023 15:41:33 -0700 Subject: [PATCH 4/4] Fixed a type on gcppubsub.md (#3596) Fixed a typo where GCP Pub/Sub was mentioned as Azure Pub/Sub Signed-off-by: jjkcharles <1765598+jjkcharles@users.noreply.github.com> --- .../components-reference/supported-bindings/gcppubsub.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/gcppubsub.md b/daprdocs/content/en/reference/components-reference/supported-bindings/gcppubsub.md index 4e9e6ed2f..f1681191e 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/gcppubsub.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/gcppubsub.md @@ -9,7 +9,7 @@ aliases: ## Component format -To setup Azure Pub/Sub binding create a component of type `bindings.gcp.pubsub`. See [this guide]({{< ref "howto-bindings.md#1-create-a-binding" >}}) on how to create and apply a binding configuration. +To setup GCP Pub/Sub binding create a component of type `bindings.gcp.pubsub`. See [this guide]({{< ref "howto-bindings.md#1-create-a-binding" >}}) on how to create and apply a binding configuration. ```yaml