From 91d4447dc5defc67f5979b98fbcdac620aae9de6 Mon Sep 17 00:00:00 2001 From: 1046102779 Date: Mon, 1 Aug 2022 15:48:32 +0800 Subject: [PATCH 01/18] fix: typo Signed-off-by: 1046102779 Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../supported-middleware/middleware-routerchecker.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-routerchecker.md b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-routerchecker.md index 91323b93a..47c275e65 100644 --- a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-routerchecker.md +++ b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-routerchecker.md @@ -20,7 +20,7 @@ metadata: name: routerchecker spec: type: middleware.http.routerchecker - version: v1gi + version: v1 metadata: - name: rule value: "^[A-Za-z0-9/._-]+$" @@ -68,4 +68,4 @@ spec: - [Middleware]({{< ref middleware.md >}}) - [Configuration concept]({{< ref configuration-concept.md >}}) -- [Configuration overview]({{< ref configuration-overview.md >}}) \ No newline at end of file +- [Configuration overview]({{< ref configuration-overview.md >}}) From 6f1a7d393852e53e35639c1a33713626bc3af0f8 Mon Sep 17 00:00:00 2001 From: nyemade-uversky <55847877+nyemade-uversky@users.noreply.github.com> Date: Fri, 29 Jul 2022 15:34:35 -0600 Subject: [PATCH 02/18] Patch 3 (#2691) * Update release version from 1.8.2 to 1.8.3 Signed-off-by: nyemade-uversky <55847877+nyemade-uversky@users.noreply.github.com> * Update shortcode from 1.8.2 to 1.8.3 Signed-off-by: nyemade-uversky <55847877+nyemade-uversky@users.noreply.github.com> Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../content/en/operations/support/support-release-policy.md | 3 ++- daprdocs/layouts/shortcodes/dapr-latest-version.html | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/daprdocs/content/en/operations/support/support-release-policy.md b/daprdocs/content/en/operations/support/support-release-policy.md index 890f6afcf..e528e56ed 100644 --- a/daprdocs/content/en/operations/support/support-release-policy.md +++ b/daprdocs/content/en/operations/support/support-release-policy.md @@ -34,7 +34,8 @@ The table below shows the versions of Dapr releases that have been tested togeth | Release date | Runtime | CLI | SDKs | Dashboard | Status | |--------------------|:--------:|:--------|---------|---------|---------| -| July 21st 2022 | 1.8.2
| 1.8.0 | Java 1.6.0
Go 1.5.0
PHP 1.1.0
Python 1.7.0
.NET 1.8.0
JS 2.3.0 | 0.11.0 | Supported (current) | +| July 29th 2022 | 1.8.3
| 1.8.0 | Java 1.6.0
Go 1.5.0
PHP 1.1.0
Python 1.7.0
.NET 1.8.0
JS 2.3.0 | 0.11.0 | Supported (current) | +| July 21st 2022 | 1.8.2
| 1.8.0 | Java 1.6.0
Go 1.5.0
PHP 1.1.0
Python 1.7.0
.NET 1.8.0
JS 2.3.0 | 0.11.0 | Supported | | July 20th 2022 | 1.8.1
| 1.8.0 | Java 1.6.0
Go 1.5.0
PHP 1.1.0
Python 1.7.0
.NET 1.8.0
JS 2.3.0 | 0.11.0 | Supported | | July 7th 2022 | 1.8.0
| 1.8.0 | Java 1.6.0
Go 1.5.0
PHP 1.1.0
Python 1.7.0
.NET 1.8.0
JS 2.3.0 | 0.11.0 | Supported | | May 31st 2022 | 1.7.4
| 1.7.0 | Java 1.5.0
Go 1.4.0
PHP 1.1.0
Python 1.6.0
.NET 1.7.0
JS 2.2.1 | 0.10.0 | Supported | diff --git a/daprdocs/layouts/shortcodes/dapr-latest-version.html b/daprdocs/layouts/shortcodes/dapr-latest-version.html index cbc70df0e..c39b7d833 100644 --- a/daprdocs/layouts/shortcodes/dapr-latest-version.html +++ b/daprdocs/layouts/shortcodes/dapr-latest-version.html @@ -1 +1 @@ -{{- if .Get "short" }}1.8{{ else if .Get "long" }}1.8.2{{ else if .Get "cli" }}1.8.0{{ else }}1.8.2{{ end -}} +{{- if .Get "short" }}1.8{{ else if .Get "long" }}1.8.3{{ else if .Get "cli" }}1.8.0{{ else }}1.8.3{{ end -}} From 41866111a759a9e33c61fdfa87a1c56240559617 Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Thu, 14 Jul 2022 10:45:05 -0700 Subject: [PATCH 03/18] Document SignalR and Storage Queues Binding AAD Support Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../components-reference/supported-bindings/signalr.md | 7 ++++++- .../supported-bindings/storagequeues.md | 8 +++++++- 2 files changed, 13 insertions(+), 2 deletions(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md index 5151c2d02..3da5c1760 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md @@ -35,9 +35,14 @@ The above example uses secrets as plain strings. It is recommended to use a secr | Field | Required | Binding support | Details | Example | |--------------------|:--------:|------------|-----|---------| -| connectionString | Y | Output | The Azure SignalR connection string | `"Endpoint=https://.service.signalr.net;AccessKey=;Version=1.0;"` | +| connectionString | Y | Output | The Azure SignalR connection string | `"Endpoint=https://.service.signalr.net;AccessKey=;Version=1.0;"`. If the connection string does not contain the `AccessKey` option Azure Active Directory authentication will be attempted. | | hub | N | Output | Defines the hub in which the message will be send. The hub can be dynamically defined as a metadata value when publishing to an output binding (key is "hub") | `"myhub"` | +### Azure Active Directory (Azure AD) authentication + +The Azure Cosmos DB state store component supports authentication using all Azure Active Directory mechanisms. For further information and the relevant component metadata fields to provide depending on the choice of Azure AD authentication mechanism, see the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}). + +You can read additional information for setting up Cosmos DB with Azure AD authentication in the [section below](#setting-up-cosmos-db-for-authenticating-with-azure-ad). ## Binding support diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md b/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md index 947dbdf96..e46ed63d2 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md @@ -44,12 +44,18 @@ The above example uses secrets as plain strings. It is recommended to use a secr | Field | Required | Binding support | Details | Example | |--------------------|:--------:|------------|-----|---------| | storageAccount | Y | Input/Output | The Azure Storage account name | `"account1"` | -| storageAccessKey | Y | Input/Output | The Azure Storage access key | `"accessKey"` | +| storageAccessKey | Y* | Input/Output | The Azure Storage access key. Only required when not using Azure AD authentication. | `"accessKey"` | | queue | Y | Input/Output | The name of the Azure Storage queue | `"myqueue"` | | ttlInSeconds | N | Output | Parameter to set the default message time to live. If this parameter is omitted, messages will expire after 10 minutes. See [also](#specifying-a-ttl-per-message) | `"60"` | | decodeBase64 | N | Output | Configuration to decode base64 file content before saving to Blob Storage. (In case of saving a file with binary content). `true` is the only allowed positive value. Other positive variations like `"True", "1"` are not acceptable. Defaults to `false` | `true`, `false` | | queueEndpointUrl | N | Input/Output | Optional custom endpoint URL. This is useful, for example, with "[production-style URLs](https://github.com/Azure/azurite#production-style-url)" when using the [Storage emulator](https://github.com/Azure/azurite). This is also potentially useful when using custom domains for Azure Storage, although this hasn't been tested (yet). Other possible use-cases include integration testing, debugging, or any other scenario in which one might have the inclination to instruct this Dapr binding to direct its API requests to a specific URL. | `"https://accountName.queue.example.com:10001"` | +### Azure Active Directory (Azure AD) authentication + +The Azure Cosmos DB state store component supports authentication using all Azure Active Directory mechanisms. For further information and the relevant component metadata fields to provide depending on the choice of Azure AD authentication mechanism, see the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}). + +You can read additional information for setting up Cosmos DB with Azure AD authentication in the [section below](#setting-up-cosmos-db-for-authenticating-with-azure-ad). + ## Binding support This component supports both **input and output** binding interfaces. From 7ad8d6dd9c5568b2d8e6d5f75cc50e65ce966dc6 Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Tue, 2 Aug 2022 15:35:37 -0700 Subject: [PATCH 04/18] Update daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../components-reference/supported-bindings/signalr.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md index 3da5c1760..9821ffd08 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md @@ -35,7 +35,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr | Field | Required | Binding support | Details | Example | |--------------------|:--------:|------------|-----|---------| -| connectionString | Y | Output | The Azure SignalR connection string | `"Endpoint=https://.service.signalr.net;AccessKey=;Version=1.0;"`. If the connection string does not contain the `AccessKey` option Azure Active Directory authentication will be attempted. | +| connectionString | Y | Output | The Azure SignalR connection string | `"Endpoint=https://.service.signalr.net;AccessKey=;Version=1.0;"`. If the connection string does not contain the `AccessKey` option, Azure Active Directory authentication will be attempted. | | hub | N | Output | Defines the hub in which the message will be send. The hub can be dynamically defined as a metadata value when publishing to an output binding (key is "hub") | `"myhub"` | ### Azure Active Directory (Azure AD) authentication From 743130c0db9f64a8d0c41ee9cf64e2e8f7aee22f Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Tue, 2 Aug 2022 15:35:56 -0700 Subject: [PATCH 05/18] Update daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../components-reference/supported-bindings/signalr.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md index 9821ffd08..258a9ac67 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md @@ -40,7 +40,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr ### Azure Active Directory (Azure AD) authentication -The Azure Cosmos DB state store component supports authentication using all Azure Active Directory mechanisms. For further information and the relevant component metadata fields to provide depending on the choice of Azure AD authentication mechanism, see the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}). +The Azure Cosmos DB state store component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. You can read additional information for setting up Cosmos DB with Azure AD authentication in the [section below](#setting-up-cosmos-db-for-authenticating-with-azure-ad). From 10b543bfbdfadd9f4c1eea1cf197cdcc034aa1b8 Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Tue, 2 Aug 2022 15:36:06 -0700 Subject: [PATCH 06/18] Update daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../components-reference/supported-bindings/signalr.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md index 258a9ac67..920688a85 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md @@ -42,7 +42,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr The Azure Cosmos DB state store component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. -You can read additional information for setting up Cosmos DB with Azure AD authentication in the [section below](#setting-up-cosmos-db-for-authenticating-with-azure-ad). +Read more about [setting up Cosmos DB with Azure AD authentication](#setting-up-cosmos-db-for-authenticating-with-azure-ad). ## Binding support From 8e7596eb9b0fb63cc5719f35f3a7b4a20a2b6b01 Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Tue, 2 Aug 2022 15:36:21 -0700 Subject: [PATCH 07/18] Update daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../components-reference/supported-bindings/storagequeues.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md b/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md index e46ed63d2..d75ac7df0 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md @@ -52,7 +52,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr ### Azure Active Directory (Azure AD) authentication -The Azure Cosmos DB state store component supports authentication using all Azure Active Directory mechanisms. For further information and the relevant component metadata fields to provide depending on the choice of Azure AD authentication mechanism, see the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}). +The Azure Cosmos DB state store component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. You can read additional information for setting up Cosmos DB with Azure AD authentication in the [section below](#setting-up-cosmos-db-for-authenticating-with-azure-ad). From 761d12e7e5ceb7240da0723e17a686652ce16d2b Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Tue, 2 Aug 2022 15:36:29 -0700 Subject: [PATCH 08/18] Update daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../components-reference/supported-bindings/storagequeues.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md b/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md index d75ac7df0..30d4fce9d 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md @@ -54,7 +54,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr The Azure Cosmos DB state store component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. -You can read additional information for setting up Cosmos DB with Azure AD authentication in the [section below](#setting-up-cosmos-db-for-authenticating-with-azure-ad). +Read more about [setting up Cosmos DB with Azure AD authentication](#setting-up-cosmos-db-for-authenticating-with-azure-ad). ## Binding support From 543d591c7fb5a887757386574f7f03c15be9a566 Mon Sep 17 00:00:00 2001 From: Shubham Sharma Date: Fri, 29 Jul 2022 20:09:10 +0530 Subject: [PATCH 09/18] Update dapr publish CLI Signed-off-by: Shubham Sharma Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../content/en/reference/cli/dapr-publish.md | 26 ++++++++++++------- 1 file changed, 17 insertions(+), 9 deletions(-) diff --git a/daprdocs/content/en/reference/cli/dapr-publish.md b/daprdocs/content/en/reference/cli/dapr-publish.md index e70d853f9..fdf56566e 100644 --- a/daprdocs/content/en/reference/cli/dapr-publish.md +++ b/daprdocs/content/en/reference/cli/dapr-publish.md @@ -21,19 +21,27 @@ dapr publish [flags] ### Flags -| Name | Environment Variable | Default | Description | -| ------------------------ | -------------------- | ------------------------------------------------------------ | ----------------------------------------------------- | -| `--publish-app-id`, `-i` | | The ID that represents the app from which you are publishing | -| `--pubsub`, `-p` | | The name of the pub/sub component | -| `--topic`, `-t` | | | The topic to be published to | -| `--data`, `-d` | | | The JSON serialized string (optional) | -| `--data-file`, `-f` | | | A file containing the JSON serialized data (optional) | -| `--help`, `-h` | | | Print this help message | +| Name | Environment Variable | Default | Description | +| ---------------------------- | -------------------- | ------------------------------------------------------------ | ----------------------------------------------------- | +| `--publish-app-id`, `-i` | | The ID that represents the app from which you are publishing | +| `--pubsub`, `-p` | | The name of the pub/sub component | +| `--topic`, `-t` | | | The topic to be published to | +| `--data`, `-d` | | | The JSON serialized string (optional) | +| `--data-file`, `-f` | | | A file containing the JSON serialized data (optional) | +| `--help`, `-h` | | | Print this help message | +| `--metadata`, `-m` | | | A JSON serialized publish metadata (optional) | +| `--unix-domain-socket`, `-u` | | | The path to the unix domain socket (optional) | ### Examples ```bash -# Publish to sample topic in target pubsub +# Publish to sample topic in target pubsub via a publishing app dapr publish --publish-app-id appId --topic sample --pubsub target --data '{"key":"value"}' + +# Publish to sample topic in target pubsub via a publishing app using Unix domain socket +dapr publish --enable-domain-socket --publish-app-id myapp --pubsub target --topic sample --data '{"key":"value"}' + +# Publish to sample topic in target pubsub via a publishing app without cloud event +dapr publish --publish-app-id myapp --pubsub target --topic sample --data '{"key":"value"}' --metadata '{"rawPayload":"true"}' ``` From 88825e7225ee9a77da2c13f72e0ead4c498a6c48 Mon Sep 17 00:00:00 2001 From: Addison Juarez Date: Fri, 29 Jul 2022 09:36:11 -0500 Subject: [PATCH 10/18] Update cassandra to Beta Signed-off-by: Addison Juarez Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- daprdocs/data/components/state_stores/generic.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/data/components/state_stores/generic.yaml b/daprdocs/data/components/state_stores/generic.yaml index 6b524549a..6fde1ab0f 100644 --- a/daprdocs/data/components/state_stores/generic.yaml +++ b/daprdocs/data/components/state_stores/generic.yaml @@ -11,7 +11,7 @@ query: false - component: Apache Cassandra link: setup-cassandra - state: Alpha + state: Beta version: v1 since: "1.0" features: From 78614af95f88ab2906fb61c40339e02f25173a64 Mon Sep 17 00:00:00 2001 From: Addison Juarez Date: Wed, 3 Aug 2022 13:57:46 -0500 Subject: [PATCH 11/18] update to 1.9 Signed-off-by: Addison Juarez Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- daprdocs/data/components/state_stores/generic.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/data/components/state_stores/generic.yaml b/daprdocs/data/components/state_stores/generic.yaml index 6fde1ab0f..0dc5820b6 100644 --- a/daprdocs/data/components/state_stores/generic.yaml +++ b/daprdocs/data/components/state_stores/generic.yaml @@ -13,7 +13,7 @@ link: setup-cassandra state: Beta version: v1 - since: "1.0" + since: "1.9" features: crud: true transactions: false From 69a312918a0248b0f930e9318fe4f59f7968153a Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Wed, 3 Aug 2022 12:48:34 -0700 Subject: [PATCH 12/18] Update daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../components-reference/supported-bindings/signalr.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md index 920688a85..e74bedec6 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md @@ -40,7 +40,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr ### Azure Active Directory (Azure AD) authentication -The Azure Cosmos DB state store component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. +The Azure SignalR binding component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. Read more about [setting up Cosmos DB with Azure AD authentication](#setting-up-cosmos-db-for-authenticating-with-azure-ad). From fc20decd7d659adfb3d5791881ad28f81ca08f7c Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Wed, 3 Aug 2022 12:48:44 -0700 Subject: [PATCH 13/18] Update daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../components-reference/supported-bindings/storagequeues.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md b/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md index 30d4fce9d..29b77d780 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md @@ -52,7 +52,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr ### Azure Active Directory (Azure AD) authentication -The Azure Cosmos DB state store component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. +The Azure Storage queue binding component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. Read more about [setting up Cosmos DB with Azure AD authentication](#setting-up-cosmos-db-for-authenticating-with-azure-ad). From 7f0133102b771c08fea93d163526455caadd5763 Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Wed, 3 Aug 2022 12:50:34 -0700 Subject: [PATCH 14/18] Update daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../components-reference/supported-bindings/storagequeues.md | 1 - 1 file changed, 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md b/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md index 29b77d780..ba491e596 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md @@ -54,7 +54,6 @@ The above example uses secrets as plain strings. It is recommended to use a secr The Azure Storage queue binding component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. -Read more about [setting up Cosmos DB with Azure AD authentication](#setting-up-cosmos-db-for-authenticating-with-azure-ad). ## Binding support From fa9e06196dfa140c8870b707211ee421a82cf07e Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Wed, 3 Aug 2022 12:50:49 -0700 Subject: [PATCH 15/18] Update daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../components-reference/supported-bindings/storagequeues.md | 1 - 1 file changed, 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md b/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md index ba491e596..224f5d4d4 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md @@ -54,7 +54,6 @@ The above example uses secrets as plain strings. It is recommended to use a secr The Azure Storage queue binding component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. - ## Binding support This component supports both **input and output** binding interfaces. From c7969869d146b8d88e434ab6b969794bb913f965 Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Wed, 3 Aug 2022 12:51:55 -0700 Subject: [PATCH 16/18] Update daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../reference/components-reference/supported-bindings/signalr.md | 1 - 1 file changed, 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md index e74bedec6..8155e1bae 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md @@ -42,7 +42,6 @@ The above example uses secrets as plain strings. It is recommended to use a secr The Azure SignalR binding component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. -Read more about [setting up Cosmos DB with Azure AD authentication](#setting-up-cosmos-db-for-authenticating-with-azure-ad). ## Binding support From 306f6ebcf536441e85f94b4224e4f506450cc430 Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Wed, 3 Aug 2022 12:52:16 -0700 Subject: [PATCH 17/18] Update daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../reference/components-reference/supported-bindings/signalr.md | 1 - 1 file changed, 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md index 8155e1bae..660556fc7 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md @@ -42,7 +42,6 @@ The above example uses secrets as plain strings. It is recommended to use a secr The Azure SignalR binding component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. - ## Binding support This component supports **output binding** with the following operations: From d63d5815cc0e22e7018bae47e856b21a654be1c8 Mon Sep 17 00:00:00 2001 From: Bernd Verst <4535280+berndverst@users.noreply.github.com> Date: Wed, 3 Aug 2022 12:52:43 -0700 Subject: [PATCH 18/18] Update daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com> --- .../reference/components-reference/supported-bindings/signalr.md | 1 + 1 file changed, 1 insertion(+) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md index 660556fc7..8155e1bae 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md @@ -42,6 +42,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr The Azure SignalR binding component supports authentication using all Azure Active Directory mechanisms. See the [docs for authenticating to Azure]({{< ref authenticating-azure.md >}}) to learn more about the relevant component metadata fields based on your choice of Azure AD authentication mechanism. + ## Binding support This component supports **output binding** with the following operations: