From 63a6b4732e759c31d7926bce009db9b4a3c11d55 Mon Sep 17 00:00:00 2001 From: Javier Vela Date: Wed, 11 Aug 2021 19:08:02 +0200 Subject: [PATCH 1/3] updated binding smtp doc: added priority option (#1666) * updated binding smtp doc: added priority option * Update daprdocs/content/en/reference/components-reference/supported-bindings/smtp.md Co-authored-by: Aaron Crawfis * Update daprdocs/content/en/reference/components-reference/supported-bindings/smtp.md Co-authored-by: Aaron Crawfis * Update daprdocs/content/en/reference/components-reference/supported-bindings/smtp.md Co-authored-by: Ori Zohar Co-authored-by: Aaron Crawfis Co-authored-by: Ori Zohar --- .../components-reference/supported-bindings/smtp.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/smtp.md b/daprdocs/content/en/reference/components-reference/supported-bindings/smtp.md index 822b2df0e..205fb002e 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/smtp.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/smtp.md @@ -42,6 +42,8 @@ spec: value: "bcc@example.com" - name: subject value: "subject" + - name: priority + value: "[value 1-5]" ``` {{% alert title="Warning" color="warning" %}} @@ -62,6 +64,7 @@ The example configuration shown above, contain a username and password as plain- | emailCc | N | Output | If set, this specifies the email address to CC in. See [also](#example-request) | `"me@example.com"` | | emailBcc | N | Output | If set, this specifies email address to BCC in. See [also](#example-request) | `"me@example.com"` | | subject | N | Output | If set, this specifies the subject of the email message. See [also](#example-request) | `"subject of mail"` | +| priority | N | Output | If set, this specifies the priority (X-Priority) of the email message, from 1 (lowest) to 5 (highest) (default value: 3). See [also](#example-request) | `"1"` | ## Binding support @@ -78,6 +81,7 @@ You can specify any of the following optional metadata properties with each requ - `emailCC` - `emailBCC` - `subject` +- `priority` When sending an email, the metadata in the configuration and in the request is combined. The combined set of metadata must contain at least the `emailFrom`, `emailTo` and `subject` fields. @@ -90,7 +94,8 @@ Example: "metadata": { "emailTo": "dapr-smtp-binding@example.net", "emailCC": "cc1@example.net; cc2@example.net", - "subject": "Email subject" + "subject": "Email subject", + "priority: "1" }, "data": "Testing Dapr SMTP Binding" } From c6f7ed545ec73924759391308ec7d60e0cb71ab6 Mon Sep 17 00:00:00 2001 From: Rishabh Saha Date: Sun, 15 Aug 2021 09:36:24 -0400 Subject: [PATCH 2/3] Redis component needs to include enableTLS:true for Azure Redis Cache Hi, proposing this PR in regards to the issue created : https://github.com/dapr/docs/issues/1719#issuecomment-898736256 --- .../en/getting-started/configure-state-pubsub.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/daprdocs/content/en/getting-started/configure-state-pubsub.md b/daprdocs/content/en/getting-started/configure-state-pubsub.md index 2b49fced2..d227166dc 100644 --- a/daprdocs/content/en/getting-started/configure-state-pubsub.md +++ b/daprdocs/content/en/getting-started/configure-state-pubsub.md @@ -125,6 +125,9 @@ spec: secretKeyRef: name: redis key: redis-password + # uncomment below for connecting to redis cache instances over TLS (ex - Azure Redis Cache) + # - name: enableTLS + # value: true ``` This example uses the kubernetes secret that was created when setting up a cluster with the above instructions. @@ -153,6 +156,9 @@ spec: secretKeyRef: name: redis key: redis-password + # uncomment below for connecting to redis cache instances over TLS (ex - Azure Redis Cache) + # - name: enableTLS + # value: true ``` This example uses the kubernetes secret that was created when setting up a cluster with the above instructions. @@ -179,6 +185,9 @@ spec: value: - name: redisPassword value: + # uncomment below for connecting to redis cache instances over TLS (ex - Azure Redis Cache) + # - name: enableTLS + # value: true ``` ```yaml @@ -195,6 +204,9 @@ spec: value: - name: redisPassword value: + # uncomment below for connecting to redis cache instances over TLS (ex - Azure Redis Cache) + # - name: enableTLS + # value: true ``` ## Apply the configuration From 1bf2d215e98dd31b3299029df4e6b8d2ed2a39a7 Mon Sep 17 00:00:00 2001 From: Simon Leet Date: Wed, 18 Aug 2021 15:41:43 -0700 Subject: [PATCH 3/3] Fix casing typo in OPA rego example for Authorization --- .../components-reference/supported-middleware/middleware-opa.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-opa.md b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-opa.md index 54b042284..efa945bcd 100644 --- a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-opa.md +++ b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-opa.md @@ -61,7 +61,7 @@ spec: my_claim := jwt.payload["my-claim"] } jwt = { "payload": payload } { - auth_header := input.request.headers["authorization"] + auth_header := input.request.headers["Authorization"] [_, jwt] := split(auth_header, " ") [_, payload, _] := io.jwt.decode(jwt) }