dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'v1.11' into ts-azure-app-config-subscribe-interval

This commit is contained in:
Hannah Hunter 2023-07-05 13:48:14 -04:00 committed by GitHub
parent 48d1443ea4 044fac582a
commit 8780bf5ff3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
daprdocs/content/en/reference/components-reference/supported-bindings/gcppubsub.md
View File

@ -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

3
daprdocs/content/en/reference/components-reference/supported-bindings/rabbitmq.md
View File

@ -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 are 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.

6
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-aws-snssqs.md
View File

@ -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