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

Merge branch 'v1.8' into feature/typo

This commit is contained in:
greenie-msft 2022-08-02 09:09:21 -07:00 committed by GitHub
parent 5b0ab10cfa c833f83b24
commit 3ca9888dc6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
114 changed files with 238 additions and 181 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
daprdocs/content/en/developing-applications/building-blocks/bindings/howto-bindings.md
View File

@ -249,7 +249,7 @@ func main() {
```javascript
//dependencies
import { DaprClient, CommunicationProtocolEnum } from "dapr-client";
import { DaprClient, CommunicationProtocolEnum } from "@dapr/dapr";
//code
const daprHost = "127.0.0.1";

2
daprdocs/content/en/developing-applications/building-blocks/bindings/howto-triggers.md
View File

@ -223,7 +223,7 @@ func main() {
```javascript
//dependencies
import { DaprServer, CommunicationProtocolEnum } from 'dapr-client';
import { DaprServer, CommunicationProtocolEnum } from '@dapr/dapr';
//code
const daprHost = "127.0.0.1";

6
daprdocs/content/en/developing-applications/building-blocks/distributed-lock/howto-use-distributed-lock.md
View File

@ -6,9 +6,9 @@ weight: 2000
description: "Learn how to use distributed locks to provide exclusive access to a resource"
---
Now that you've learned what the Dapr distributed lock API building block provides, learn how it can work in your service. The example below describes an application that aquires a lock. This example uses the Redis lock component to demonstrate how to lock resources. For a list of supported lock stores, see [this list](/reference/components-reference/supported-locks/).
Now that you've learned what the Dapr distributed lock API building block provides, learn how it can work in your service. In this guide, an example application acquires a lock using the Redis lock component to demonstrate how to lock resources. For a list of supported lock stores, see [this reference page](/reference/components-reference/supported-locks/).
The diagram below shows two instances of the same application acquiring a lock, where one instance is successful and the other is denied.
In the diagram below, two instances of the same application acquire a lock, where one instance is successful and the other is denied.
<img src="/images/building-block-lock-example.png" width=1000 alt="The diagram below shows two instances of the same application acquiring a lock, where one instance is successful and the other is denied">
@ -188,4 +188,4 @@ func main() {
## Next steps
* Read [distributed lock API overview]({{< ref distributed-lock-api-overview.md >}})
Read [the distributed lock API overview]({{< ref distributed-lock-api-overview.md >}}) to learn more.

5
daprdocs/content/en/developing-applications/building-blocks/pubsub/howto-publish-subscribe.md
View File

@ -118,7 +118,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: order-pub-sub
namespace: default
spec:
type: pubsub.rabbitmq
version: v1
@ -334,7 +333,7 @@ dapr run --app-id checkout --app-port 6002 --dapr-http-port 3602 --dapr-grpc-por
```javascript
//dependencies
import { DaprServer, CommunicationProtocolEnum } from 'dapr-client';
import { DaprServer, CommunicationProtocolEnum } from '@dapr/dapr';
//code
const daprHost = "127.0.0.1";
@ -599,7 +598,7 @@ dapr run --app-id orderprocessing --app-port 6001 --dapr-http-port 3601 --dapr-g
```javascript
//dependencies
import { DaprServer, DaprClient, CommunicationProtocolEnum } from 'dapr-client';
import { DaprServer, DaprClient, CommunicationProtocolEnum } from '@dapr/dapr';
const daprHost = "127.0.0.1";

3
daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-scopes.md
View File

@ -48,7 +48,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: pubsub
namespace: default
spec:
type: pubsub.redis
version: v1
@ -95,7 +94,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: pubsub
namespace: default
spec:
type: pubsub.redis
version: v1
@ -120,7 +118,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: pubsub
namespace: default
spec:
type: pubsub.redis
version: v1

3
daprdocs/content/en/developing-applications/building-blocks/secrets/howto-secrets.md
View File

@ -38,7 +38,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: localsecretstore
namespace: default
spec:
type: secretstores.local.file
version: v1
@ -210,7 +209,7 @@ func main() {
```javascript
//dependencies
import { DaprClient, HttpMethod, CommunicationProtocolEnum } from 'dapr-client';
import { DaprClient, HttpMethod, CommunicationProtocolEnum } from '@dapr/dapr';
//code
const daprHost = "127.0.0.1";

2
daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-discover-services.md
View File

@ -331,7 +331,7 @@ func main() {
```javascript
//dependencies
import { DaprClient, HttpMethod, CommunicationProtocolEnum } from 'dapr-client';
import { DaprClient, HttpMethod, CommunicationProtocolEnum } from '@dapr/dapr';
//code
const daprHost = "127.0.0.1";

9
daprdocs/content/en/developing-applications/building-blocks/state-management/howto-get-save-state.md
View File

@ -44,7 +44,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: statestore
namespace: default
spec:
type: state.redis
version: v1
@ -251,7 +250,7 @@ dapr run --app-id orderprocessing --app-port 6001 --dapr-http-port 3601 --dapr-g
```javascript
//dependencies
import { DaprClient, HttpMethod, CommunicationProtocolEnum } from 'dapr-client';
import { DaprClient, HttpMethod, CommunicationProtocolEnum } from '@dapr/dapr';
//code
const daprHost = "127.0.0.1";
@ -477,7 +476,7 @@ dapr run --app-id orderprocessing --app-port 6001 --dapr-http-port 3601 --dapr-g
```javascript
//dependencies
import { DaprClient, HttpMethod, CommunicationProtocolEnum } from 'dapr-client';
import { DaprClient, HttpMethod, CommunicationProtocolEnum } from '@dapr/dapr';
//code
const daprHost = "127.0.0.1";
@ -623,7 +622,7 @@ dapr run --app-id orderprocessing --app-port 6001 --dapr-http-port 3601 --dapr-g
```javascript
//dependencies
import { DaprClient, HttpMethod, CommunicationProtocolEnum } from 'dapr-client';
import { DaprClient, HttpMethod, CommunicationProtocolEnum } from '@dapr/dapr';
//code
const daprHost = "127.0.0.1";
@ -855,7 +854,7 @@ dapr run --app-id orderprocessing --app-port 6001 --dapr-http-port 3601 --dapr-g
```javascript
//dependencies
import { DaprClient, HttpMethod, CommunicationProtocolEnum } from 'dapr-client';
import { DaprClient, HttpMethod, CommunicationProtocolEnum } from '@dapr/dapr';
//code
const daprHost = "127.0.0.1";

4
daprdocs/content/en/getting-started/install-dapr-cli.md
View File

@ -74,7 +74,7 @@ curl -fsSL https://raw.githubusercontent.com/dapr/cli/master/install/install.sh
**For ARM64 Macs:**
ARM64 Macs support is available as a *preview feature*. When installing from the terminal, native ARM64 binaries are downloaded once available. For older releases, AMD64 binaries are downloaded and must be run with Rosetta2 emulation enabled.
When installing from the terminal, native ARM64 binaries are available.
To install Rosetta emulation:
@ -92,7 +92,7 @@ brew install dapr/tap/dapr-cli
**For ARM64 Macs:**
For ARM64 Macs, only Homebrew 3.0 and higher versions are supported. Please update Homebrew to 3.0.0 or higher and then run the command below:
For ARM64 Macs, Homebrew 3.0 and higher versions are supported. Update Homebrew to 3.0.0 or higher and then run the command below:
```bash
arch -arm64 brew install dapr/tap/dapr-cli

2
daprdocs/content/en/getting-started/quickstarts/bindings-quickstart.md
View File

@ -88,6 +88,8 @@ Run the `batch-sdk` service alongside a Dapr sidecar.
dapr run --app-id batch-sdk --app-port 50051 --components-path ../../../components -- python3 app.py
```
> **Note**: Since Python3.exe is not defined in Windows, you may need to use `python app.py` instead of `python3 app.py`.
The code inside the `process_batch` function is executed every 10 seconds (defined in [`binding-cron.yaml`]({{< ref "#componentsbinding-cronyaml-component-file" >}}) in the `components` directory). The binding trigger looks for a route called via HTTP POST in your Flask application by the Dapr sidecar.
```python

8
daprdocs/content/en/getting-started/quickstarts/pubsub-quickstart.md
View File

@ -59,6 +59,8 @@ Run the `order-processor` subscriber service alongside a Dapr sidecar.
dapr run --app-id order-processor --components-path ../../../components/ --app-port 5001 -- python3 app.py
```
> **Note**: Since Python3.exe is not defined in Windows, you may need to use `python app.py` instead of `python3 app.py`.
In the `order-processor` subscriber, we're subscribing to the Redis instance called `order_pub_sub` [(as defined in the `pubsub.yaml` component)]({{< ref "#pubsubyaml-component-file" >}}) and topic `orders`. This enables your app code to talk to the Redis component instance through the Dapr sidecar.
```py
@ -106,6 +108,8 @@ Run the `checkout` publisher service alongside a Dapr sidecar.
dapr run --app-id checkout --components-path ../../../components/ -- python3 app.py
```
> **Note**: Since Python3.exe is not defined in Windows, you may need to use `python app.py` instead of `python3 app.py`.
In the `checkout` publisher, we're publishing the orderId message to the Redis instance called `order_pub_sub` [(as defined in the `pubsub.yaml` component)]({{< ref "#pubsubyaml-component-file" >}}) and topic `orders`. As soon as the service starts, it publishes in a loop:
```python
@ -217,7 +221,7 @@ navigate to the `order-processor` directory.
cd pub_sub/javascript/sdk/order-processor
```
Install dependencies, which will include the `dapr-client` package from the JavaScript SDK:
Install dependencies, which will include the `@dapr/dapr` package from the JavaScript SDK:
```bash
npm install
@ -249,7 +253,7 @@ navigate to the `checkout` directory.
cd pub_sub/javascript/sdk/checkout
```
Install dependencies, which will include the `dapr-client` package from the JavaScript SDK:
Install dependencies, which will include the `@dapr/dapr` package from the JavaScript SDK:
```bash
npm install

23
daprdocs/content/en/getting-started/quickstarts/secrets-quickstart.md
View File

@ -55,6 +55,9 @@ Run the `order-processor` service alongside a Dapr sidecar.
dapr run --app-id order-processor --components-path ../../../components/ -- python3 app.py
```
> **Note**: Since Python3.exe is not defined in Windows, you may need to use `python app.py` instead of `python3 app.py`.
#### Behind the scenes
**`order-processor` service**
@ -75,7 +78,7 @@ with DaprClient() as client:
**`local-secret-store.yaml` component**
`DAPR_SECRET_STORE` is defined in the `local-secret-store.yaml` component file, located in [secrets_management/components](https://github.com/dapr/quickstarts/blob/master/secrets_management/components/local-secret-store.yaml):
`DAPR_SECRET_STORE` is defined in the `local-secret-store.yaml` component file, located in [secrets_management/components](https://github.com/dapr/quickstarts/tree/master/secrets_management/components/local-secret-store.yaml):
```yaml
apiVersion: dapr.io/v1alpha1
@ -100,7 +103,7 @@ In the YAML file:
**`secrets.json` file**
`SECRET_NAME` is defined in the `secrets.json` file, located in [secrets_management/python/sdk/order-processor](https://github.com/dapr/quickstarts/blob/master/secrets_management/python/sdk/order-processor/secrets.json):
`SECRET_NAME` is defined in the `secrets.json` file, located in [secrets_management/python/sdk/order-processor](https://github.com/dapr/quickstarts/tree/master/secrets_management/javascript/sdk/order-processor/secrets.json):
```json
{
@ -184,7 +187,7 @@ async function main() {
**`local-secret-store.yaml` component**
`DAPR_SECRET_STORE` is defined in the `local-secret-store.yaml` component file, located in [secrets_management/components](https://github.com/dapr/quickstarts/blob/master/secrets_management/components/local-secret-store.yaml):
`DAPR_SECRET_STORE` is defined in the `local-secret-store.yaml` component file, located in [secrets_management/components](https://github.com/dapr/quickstarts/tree/master/secrets_management/components/local-secret-store.yaml):
```yaml
apiVersion: dapr.io/v1alpha1
@ -209,7 +212,7 @@ In the YAML file:
**`secrets.json` file**
`SECRET_NAME` is defined in the `secrets.json` file, located in [secrets_management/javascript/sdk/order-processor](https://github.com/dapr/quickstarts/blob/master/secrets_management/javascript/sdk/order-processor/secrets.json):
`SECRET_NAME` is defined in the `secrets.json` file, located in [secrets_management/javascript/sdk/order-processor](https://github.com/dapr/quickstarts/tree/master/secrets_management/javascript/sdk/order-processor/secrets.json):
```json
{
@ -297,7 +300,7 @@ Console.WriteLine($"Fetched Secret: {secretValue}");
**`local-secret-store.yaml` component**
`DAPR_SECRET_STORE` is defined in the `local-secret-store.yaml` component file, located in [secrets_management/components](https://github.com/dapr/quickstarts/blob/master/secrets_management/components/local-secret-store.yaml):
`DAPR_SECRET_STORE` is defined in the `local-secret-store.yaml` component file, located in [secrets_management/components](https://github.com/dapr/quickstarts/tree/master/secrets_management/components/local-secret-store.yaml):
```yaml
apiVersion: dapr.io/v1alpha1
@ -322,7 +325,7 @@ In the YAML file:
**`secrets.json` file**
`SECRET_NAME` is defined in the `secrets.json` file, located in [secrets_management/csharp/sdk/order-processor](https://github.com/dapr/quickstarts/blob/master/secrets_management/csharp/sdk/order-processor/secrets.json):
`SECRET_NAME` is defined in the `secrets.json` file, located in [secrets_management/csharp/sdk/order-processor](https://github.com/dapr/quickstarts/tree/master/secrets_management/javascript/sdk/order-processor/secrets.json):
```json
{
@ -405,7 +408,7 @@ private static final String SECRET_STORE_NAME = "localsecretstore";
**`local-secret-store.yaml` component**
`DAPR_SECRET_STORE` is defined in the `local-secret-store.yaml` component file, located in [secrets_management/components](https://github.com/dapr/quickstarts/blob/master/secrets_management/components/local-secret-store.yaml):
`DAPR_SECRET_STORE` is defined in the `local-secret-store.yaml` component file, located in [secrets_management/components](https://github.com/dapr/quickstarts/tree/master/secrets_management/components/local-secret-store.yaml):
```yaml
apiVersion: dapr.io/v1alpha1
@ -430,7 +433,7 @@ In the YAML file:
**`secrets.json` file**
`SECRET_NAME` is defined in the `secrets.json` file, located in [secrets_management/python/sdk/order-processor](https://github.com/dapr/quickstarts/blob/master/secrets_management/java/sdk/order-processor/secrets.json):
`SECRET_NAME` is defined in the `secrets.json` file, located in [secrets_management/python/sdk/order-processor](https://github.com/dapr/quickstarts/tree/master/secrets_management/javascript/sdk/order-processor/secrets.json):
```json
{
@ -512,7 +515,7 @@ const DAPR_SECRET_STORE = "localsecretstore"
**`local-secret-store.yaml` component**
`DAPR_SECRET_STORE` is defined in the `local-secret-store.yaml` component file, located in [secrets_management/components](https://github.com/dapr/quickstarts/blob/master/secrets_management/components/local-secret-store.yaml):
`DAPR_SECRET_STORE` is defined in the `local-secret-store.yaml` component file, located in [secrets_management/components](https://github.com/dapr/quickstarts/tree/master/secrets_management/components/local-secret-store.yaml):
```yaml
apiVersion: dapr.io/v1alpha1
@ -537,7 +540,7 @@ In the YAML file:
**`secrets.json` file**
`SECRET_NAME` is defined in the `secrets.json` file, located in [secrets_management/python/sdk/order-processor](https://github.com/dapr/quickstarts/blob/master/secrets_management/java/sdk/order-processor/secrets.json):
`SECRET_NAME` is defined in the `secrets.json` file, located in [secrets_management/python/sdk/order-processor](https://github.com/dapr/quickstarts/tree/master/secrets_management/javascript/sdk/order-processor/secrets.json):
```json
{

4
daprdocs/content/en/getting-started/quickstarts/serviceinvocation-quickstart.md
View File

@ -59,6 +59,8 @@ Run the `order-processor` service alongside a Dapr sidecar.
dapr run --app-port 7001 --app-id order-processor --app-protocol http --dapr-http-port 3501 -- python3 app.py
```
> **Note**: Since Python3.exe is not defined in Windows, you may need to use `python app.py` instead of `python3 app.py`.
```py
@app.route('/orders', methods=['POST'])
def getOrder():
@ -92,6 +94,8 @@ Run the `checkout` service alongside a Dapr sidecar.
dapr run --app-id checkout --app-protocol http --dapr-http-port 3500 -- python3 app.py
```
> **Note**: Since Python3.exe is not defined in Windows, you may need to use `python app.py` instead of `python3 app.py`.
In the `checkout` service, you'll notice there's no need to rewrite your app code to use Dapr's service invocation. You can enable service invocation by simply adding the `dapr-app-id` header, which specifies the ID of the target service.
```python

4
daprdocs/content/en/getting-started/quickstarts/statemanagement-quickstart.md
View File

@ -54,6 +54,8 @@ Run the `order-processor` service alongside a Dapr sidecar.
dapr run --app-id order-processor --components-path ../../../components/ -- python3 app.py
```
> **Note**: Since Python3.exe is not defined in Windows, you may need to use `python app.py` instead of `python3 app.py`.
The `order-processor` service writes, reads, and deletes an `orderId` key/value pair to the `statestore` instance [defined in the `statestore.yaml` component]({{< ref "#statestoreyaml-component-file" >}}). As soon as the service starts, it performs a loop.
```python
@ -156,7 +158,7 @@ In a terminal window, navigate to the `order-processor` directory.
cd state_management/javascript/sdk/order-processor
```
Install dependencies, which will include the `dapr-client` package from the JavaScript SDK:
Install dependencies, which will include the `@dapr/dapr` package from the JavaScript SDK:
```bash
npm install

3
daprdocs/content/en/operations/components/component-secrets.md
View File

@ -27,7 +27,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: statestore
namespace: default
spec:
type: state.redis
version: v1
@ -47,7 +46,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: statestore
namespace: default
spec:
type: state.redis
version: v1
@ -106,7 +104,6 @@ The following example shows you how to create a Kubernetes secret to hold the co
kind: Component
metadata:
name: eventhubs
namespace: default
spec:
type: bindings.azure.eventhubs
version: v1

1
daprdocs/content/en/operations/components/setup-bindings.md
View File

@ -38,7 +38,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.azure.blobstorage
version: v1

2
daprdocs/content/en/operations/components/setup-secret-store.md
View File

@ -19,7 +19,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: secretstore
namespace: default
spec:
type: secretstores.<NAME>
version: v1
@ -40,7 +39,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: awssecretmanager
namespace: default
spec:
type: secretstores.aws.secretmanager
version: v1

1
daprdocs/content/en/operations/components/setup-state-store.md
View File

@ -19,7 +19,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: statestore
namespace: default
spec:
type: state.<DATABASE>
version: v1

21
daprdocs/content/en/operations/configuration/install-certificates.md
View File

@ -80,18 +80,29 @@ spec:
...
```
{{% alert title="Note" color="primary" %}}
When using Windows containers, the sidecar container is started with admin privileges, which is required to install the certificates. This does not apply to Linux containers.
{{% /alert %}}
**Note**: When using Windows containers, the sidecar container is started with admin privileges, which is required to install the certificates. This does not apply to Linux containers.
{{% /codetab %}}
Note, all the certificates in the directory pointed by `SSL_CERT_DIR` are installed.
{{< /tabs >}}
<hr/>
All the certificates in the directory pointed by `SSL_CERT_DIR` are installed.
1. On Linux containers, all the certificate extensions supported by OpenSSL are supported. For more information, see https://www.openssl.org/docs/man1.1.1/man1/openssl-rehash.html
1. On Windows container, all the certificate extensions supported by certoc.exe are supported. For more information, see certoc.exe present in [Windows Server Core](https://hub.docker.com/_/microsoft-windows-servercore)
{{< /tabs >}}
## Example
Watch the demo on using installing SSL certificates and securely using the HTTP binding in community call 64:
<div class="embed-responsive embed-responsive-16by9">
<iframe width="560" height="315" src="https://www.youtube.com/embed/M0VM7GlphAU?start=800" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
## Related links
- [HTTP binding spec]({{< ref http.md >}})
- [(Kubernetes) How-to: Mount Pod volumes to the Dapr sidecar]({{< ref kubernetes-volume-mounts.md >}})
- [Dapr Kubernetes pod annotations spec]({{< ref arguments-annotations-overview.md >}})

1
daprdocs/content/en/operations/hosting/kubernetes/kubernetes-volume-mounts.md
View File

@ -92,7 +92,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: local-secret-store
namespace: default
spec:
type: secretstores.local.file
version: v1

11
daprdocs/content/en/operations/hosting/self-hosted/self-hosted-with-docker.md
View File

@ -120,12 +120,13 @@ services:
image: "daprio/daprd:edge"
command: [
"./daprd",
"-app-id", "nodeapp",
"-app-port", "3000",
"-placement-host-address", "placement:50006" # Dapr's placement service can be reach via the docker DNS entry
"--app-id", "nodeapp",
"--app-port", "3000",
"--placement-host-address", "placement:50006", # Dapr's placement service can be reach via the docker DNS entry
"--components-path", "./components"
]
volumes:
- "./components/:/components" # Mount our components folder for the runtime to use
- "./components/:/components" # Mount our components folder for the runtime to use. The mounted location must match the --components-path argument.
depends_on:
- nodeapp
network_mode: "service:nodeapp" # Attach the nodeapp-dapr service to the nodeapp network namespace
@ -134,7 +135,7 @@ services:
placement:
image: "daprio/dapr"
command: ["./placement", "-port", "50006"]
command: ["./placement", "--port", "50006"]
ports:
- "50006:50006"

60
daprdocs/content/en/operations/support/support-release-policy.md
View File

@ -8,7 +8,7 @@ description: "Runtime and SDK release support and upgrade policies "
## Introduction
This topic details the supported versions of Dapr releases, the upgrade policies, and how deprecations and breaking changes are communicated.
This topic details the supported versions of Dapr releases, the upgrade policies and how deprecations and breaking changes are communicated in all Dapr repositories (runtime, CLI, SDKs, etc) at versions 1.x and above.
Dapr releases use `MAJOR.MINOR.PATCH` versioning. For example, 1.0.0.
@ -16,7 +16,7 @@ Dapr releases use `MAJOR.MINOR.PATCH` versioning. For example, 1.0.0.
| ---------- | ----------- |
| `MAJOR` | Updated when there’s a non-backward compatible change to the runtime, such as an API change. A `MAJOR` release can also occur then there is a considered a significant addition/change of functionality that needs to differentiate from the previous version. |
| `MINOR` | Updated as part of the regular release cadence, including new features, bug, and security fixes. |
| `PATCH` | Incremented for bug and security hot fixes. |
| `PATCH` | Incremented for a critical issue (P0) and security hot fixes. |
A supported release means:
@ -30,11 +30,14 @@ There will be at least 6 weeks between major.minor version releases giving users
Patch support is for supported versions (current and previous).
## Supported versions
The table below shows the versions of Dapr releases that have been tested together and form a "packaged" release. Any other combinations of releases are not supported.
| Release date | Runtime | CLI | SDKs | Dashboard | Status |
|--------------------|:--------:|:--------|---------|---------|---------|
| July 20th 2022 | 1.8.1</br> | 1.8.0 | Java 1.6.0 </br>Go 1.5.0 </br>PHP 1.1.0 </br>Python 1.7.0 </br>.NET 1.8.0 </br>JS 2.3.0 | 0.11.0 | Supported (current) |
| July 29th 2022 | 1.8.3</br> | 1.8.0 | Java 1.6.0 </br>Go 1.5.0 </br>PHP 1.1.0 </br>Python 1.7.0 </br>.NET 1.8.0 </br>JS 2.3.0 | 0.11.0 | Supported (current) |
| July 21st 2022 | 1.8.2</br> | 1.8.0 | Java 1.6.0 </br>Go 1.5.0 </br>PHP 1.1.0 </br>Python 1.7.0 </br>.NET 1.8.0 </br>JS 2.3.0 | 0.11.0 | Supported |
| July 20th 2022 | 1.8.1</br> | 1.8.0 | Java 1.6.0 </br>Go 1.5.0 </br>PHP 1.1.0 </br>Python 1.7.0 </br>.NET 1.8.0 </br>JS 2.3.0 | 0.11.0 | Supported |
| July 7th 2022 | 1.8.0</br> | 1.8.0 | Java 1.6.0 </br>Go 1.5.0 </br>PHP 1.1.0 </br>Python 1.7.0 </br>.NET 1.8.0 </br>JS 2.3.0 | 0.11.0 | Supported |
| May 31st 2022 | 1.7.4</br> | 1.7.0 | Java 1.5.0 </br>Go 1.4.0 </br>PHP 1.1.0 </br>Python 1.6.0 </br>.NET 1.7.0 </br>JS 2.2.1 | 0.10.0 | Supported |
| May 17th 2022 | 1.7.3</br> | 1.7.0 | Java 1.5.0 </br>Go 1.4.0 </br>PHP 1.1.0 </br>Python 1.6.0 </br>.NET 1.7.0 </br>JS 2.2.1 | 0.10.0 | Supported |
@ -56,11 +59,12 @@ The table below shows the versions of Dapr releases that have been tested togeth
| Jul 26th 2021 | 1.3</br> | 1.3.0 | Java 1.2.0 </br>Go 1.2.0 </br>PHP 1.1.0 </br>Python 1.2.0 </br>.NET 1.3.0 | 0.7.0 | Unsupported |
## Upgrade paths
After the 1.0 release of the runtime there may be situations where it is necessary to explicitly upgrade through an additional release to reach the desired target. For example, an upgrade from v1.0 to v1.2 may need to pass through v1.1.
The table below shows the tested upgrade paths for the Dapr runtime. Any other combinations of upgrades have not been tested.
General guidance on upgrading can be found for [self hosted mode]({{<ref self-hosted-upgrade>}}) and [Kubernetes]({{<ref kubernetes-upgrade>}}) deployments. It is best to review the target version release notes for specific guidance.
General guidance on upgrading can be found for [self hosted mode]({{< ref self-hosted-upgrade >}}) and [Kubernetes]({{< ref kubernetes-upgrade >}}) deployments. It is best to review the target version release notes for specific guidance.
| Current Runtime version | Must upgrade through | Target Runtime version |
|--------------------------|-----------------------|------------------------- |
@ -75,27 +79,66 @@ General guidance on upgrading can be found for [self hosted mode]({{<ref self-ho
| 1.6.0 | N/A | 1.6.2 |
| 1.6.0 | N/A | 1.7.4 |
| 1.7.0 to 1.7.4 | N/A | 1.8.0 |
| 1.8.0 | N/A | 1.8.2 |
## Feature and deprecations
There is a process for announcing feature deprecations. Deprecations are applied two (2) releases after the release in which they were announced. For example Feature X is announced to be deprecated in the 1.0.0 release notes and will then be removed in 1.2.0.
## Breaking changes and deprecations
### Breaking changes
Breaking changes are defined as a change to any of the following that cause compilation errors or undesirable runtime behavior to an existing 3rd party consumer application or script after upgrading to the next stable minor version of a Dapr artifact (SDK, CLI, runtime, etc):
- Code behavior
- Schema
- Default configuration value
- Command line argument
- Published metric
- Kubernetes CRD template
- Publicly accessible API
- Publicly visible SDK interface, method, class, or attribute
Breaking changes can be applied right away to the following cases:
- Projects versioned at 0.x.y
- Preview feature
- Alpha API
- Preview or Alpha interface, class, method or attribute in SDK
- Dapr Component in Alpha or Beta
- Components-Contrib interface
- URLs in Docs and Blog
- An **exceptional** case where it is **required** to fix a critical bug or security vulnerability.
#### Process for applying breaking changes
There is a process for applying breaking changes:
1. A deprecation notice must be posted as part of a release.
1. The breaking changes are applied two (2) releases after the release in which the deprecation was announced.
- For example, feature X is announced to be deprecated in the 1.0.0 release notes and will then be removed in 1.2.0.
### Depreciations
Deprecations appear in release notes under a section named “Deprecations”, which indicates:
- The point in the future the now-deprecated feature will no longer be supported. For example release x.y.z. This is at least two (2) releases prior.
- Document any steps the user must take to modify their code, operations, etc if applicable in the release notes.
After announcing a future breaking change, the change will happen in 2 releases or 6 months, whichever is greater. Deprecated features should respond with warning but do nothing otherwise.
### Announced deprecations
| Feature | Deprecation announcement | Removal |
|-----------------------|-----------------------|------------------------- |
| GET /v1.0/shutdown API (Users should use [POST API]({{< ref kubernetes-job.md >}}) instead) | 1.2.0 | 1.4.0 |
| Java domain builder classes deprecated (Users should use [setters](https://github.com/dapr/java-sdk/issues/587) instead) | Java SDK 1.3.0 | Java SDK 1.5.0 |
| Service invocation will no longer provide a default content type header of `application/json` when no content-type is specified. You must explictly [set a content-type header]({{<ref "service_invocation_api.md#request-contents" >}}) for service invocation if your invoked apps rely on this header. | 1.7.0 | 1.9.0 |
| Service invocation will no longer provide a default content type header of `application/json` when no content-type is specified. You must explictly [set a content-type header]({{< ref "service_invocation_api.md#request-contents" >}}) for service invocation if your invoked apps rely on this header. | 1.7.0 | 1.9.0 |
## Upgrade on Hosting platforms
Dapr can support multiple hosting platforms for production. With the 1.0 release the two supported platforms are Kubernetes and physical machines. For Kubernetes upgrades see [Production guidelines on Kubernetes]({{< ref kubernetes-production.md >}})
### Supported versions of dependencies
Below is a list of software that the latest version of Dapr (v{{% dapr-latest-version long="true" %}}) has been tested against.
| Dependency | Supported Version |
@ -105,4 +148,5 @@ Below is a list of software that the latest version of Dapr (v{{% dapr-latest-ve
| [Prometheus](https://prometheus.io/download/) | v2.28 |
## Related links
* Read the [Versioning policy]({{< ref support-versioning.md >}})
- Read the [Versioning policy]({{< ref support-versioning.md >}})

1
daprdocs/content/en/reference/api/bindings_api.md
View File

@ -56,7 +56,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: kafkaevent
namespace: default
spec:
type: bindings.kafka
version: v1

1
daprdocs/content/en/reference/api/state_api.md
View File

@ -551,7 +551,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: statestore
namespace: default
spec:
type: state.redis
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/alicloud-dingtalk.md
View File

@ -13,7 +13,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.dingtalk.webhook
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/alicloudoss.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: alicloudobjectstorage
namespace: default
spec:
type: bindings.alicloud.oss
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/alicloudtablestore.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: mytablestore
namespace: default
spec:
type: bindings.alicloud.tablestore
version: v1

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

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.apns
version: v1
@ -52,7 +51,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: apns
namespace: default
spec:
type: bindings.apns
metadata:
@ -73,7 +71,6 @@ apiVersion: v1
kind: Secret
metadata:
name: apns-secrets
namespace: default
stringData:
private-key: |
-----BEGIN PRIVATE KEY-----

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

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.azure.blobstorage
version: v1
@ -127,7 +126,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.azure.blobstorage
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/commercetools.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.commercetools
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/cosmosdb.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.azure.cosmosdb
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/cosmosdbgremlinapi.md
View File

@ -15,7 +15,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.azure.cosmosdb.gremlinapi
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/cron.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.cron
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/dynamodb.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.aws.dynamodb
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/eventhubs.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.azure.eventhubs
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/gcpbucket.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.gcp.bucket
version: v1

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

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.gcp.pubsub
version: v1

120
daprdocs/content/en/reference/components-reference/supported-bindings/http.md
View File

@ -14,7 +14,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.http
version: v1
@ -173,9 +172,126 @@ curl -d '{ "operation": "post", "data": "YOUR_BASE_64_CONTENT", "metadata": { "p
The HTTP binding can also be used with HTTPS endpoints by configuring the Dapr sidecar to trust the server's SSL certificate.
1. Update the binding component's YAML to use `https` instead of `http`
1. Update the binding URL to use `https` instead of `http`.
1. Refer [How-To: Install certificates in the Dapr sidecar]({{< ref install-certificates >}}), to install the SSL certificate in the sidecar.
### Example
#### Update the binding component
```yaml
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.http
version: v1
metadata:
- name: url
value: https://my-secured-website.com # Use HTTPS
```
#### Install the SSL certificate in the sidecar
{{< tabs Self-Hosted Kubernetes >}}
{{% codetab %}}
When the sidecar is not running inside a container, the SSL certificate can be directly installed on the host operating system.
Below is an example when the sidecar is running as a container. The SSL certificate is located on the host computer at `/tmp/ssl/cert.pem`.
```yaml
version: '3'
services:
my-app:
# ...
dapr-sidecar:
image: "daprio/daprd:1.8.0"
command: [
"./daprd",
"-app-id", "myapp",
"-app-port", "3000",
]
volumes:
- "./components/:/components"
- "/tmp/ssl/:/certificates" # Mount the certificates folder to the sidecar container at /certificates
environment:
- "SSL_CERT_DIR=/certificates" # Set the environment variable to the path of the certificates folder
depends_on:
- my-app
```
{{% /codetab %}}
{{% codetab %}}
The sidecar can read the SSL certificate from a variety of sources. See [How-to: Mount Pod volumes to the Dapr sidecar]({{< ref kubernetes-volume-mounts >}}) for more. In this example, we store the SSL certificate as a Kubernetes secret.
```bash
kubectl create secret generic myapp-cert --from-file /tmp/ssl/cert.pem
```
The YAML below is an example of the Kubernetes deployment that mounts the above secret to the sidecar and sets `SSL_CERT_DIR` to install the certificates.
```yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: myapp
namespace: default
labels:
app: myapp
spec:
replicas: 1
selector:
matchLabels:
app: myapp
template:
metadata:
labels:
app: myapp
annotations:
dapr.io/enabled: "true"
dapr.io/app-id: "myapp"
dapr.io/app-port: "8000"
dapr.io/volume-mounts: "cert-vol:/certificates" # Mount the certificates folder to the sidecar container at /certificates
dapr.io/env: "SSL_CERT_DIR=/certificates" # Set the environment variable to the path of the certificates folder
spec:
volumes:
- name: cert-vol
secret:
secretName: myapp-cert
...
```
{{% /codetab %}}
{{< /tabs >}}
#### Invoke the binding securely
{{< tabs Windows Linux >}}
{{% codetab %}}
```bash
curl -d "{ \"operation\": \"get\" }" \
https://localhost:<dapr-port>/v1.0/bindings/<binding-name>
```
{{% /codetab %}}
{{% codetab %}}
```bash
curl -d '{ "operation": "get" }' \
https://localhost:<dapr-port>/v1.0/bindings/<binding-name>
```
{{% /codetab %}}
{{< /tabs >}}
## Related links

1
daprdocs/content/en/reference/components-reference/supported-bindings/huawei-obs.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.huawei.obs
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/influxdb.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.influx
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/kafka.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: kafka-binding
namespace: default
spec:
type: bindings.kafka
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/kinesis.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.aws.kinesis
version: v1

4
daprdocs/content/en/reference/components-reference/supported-bindings/kubernetes-binding.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.kubernetes
version: v1
@ -90,7 +89,6 @@ One of the rules need to be of the form as below to give permissions to `get, wa
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
namespace: <NAMESPACE>
name: <ROLENAME>
rules:
- apiGroups: [""]
@ -105,11 +103,9 @@ apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: <NAME>
namespace: <NAMESPACE> # same as above
subjects:
- kind: ServiceAccount
name: default # or as need be, can be changed
namespace: <NAMESPACE> # same as above
roleRef:
kind: Role
name: <ROLENAME> # same as the one above

1
daprdocs/content/en/reference/components-reference/supported-bindings/localstorage.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.localstorage
version: v1

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

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.mqtt
version: v1
@ -63,7 +62,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: mqtt-binding
namespace: default
spec:
type: bindings.mqtt
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/mysql.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.mysql
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/postgres.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.postgres
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/postmark.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: postmark
namespace: default
spec:
type: bindings.postmark
metadata:

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

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.rabbitmq
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/redis.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.redis
version: v1

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

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.aws.s3
version: v1
@ -154,7 +153,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.aws.s3
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/sendgrid.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: sendgrid
namespace: default
spec:
type: bindings.twilio.sendgrid
version: v1

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

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.azure.servicebusqueues
version: v1
@ -75,7 +74,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.azure.servicebusqueues
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/ses.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: ses
namespace: default
spec:
type: bindings.aws.ses
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/signalr.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.azure.signalr
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/smtp.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: smtp
namespace: default
spec:
type: bindings.smtp
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/sns.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.aws.sns
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/sqs.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.aws.sqs
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/storagequeues.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.azure.storagequeues
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/twilio.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.twilio.sms
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/twitter.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.twitter
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/zeebe-command.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.zeebe.command
version: v1

1
daprdocs/content/en/reference/components-reference/supported-bindings/zeebe-jobworker.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.zeebe.jobworker
version: v1

1
daprdocs/content/en/reference/components-reference/supported-configuration-stores/redis-configuration-store.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: configuration.redis
version: v1

1
daprdocs/content/en/reference/components-reference/supported-locks/redis-lock.md
View File

@ -14,7 +14,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: lock.redis
version: v1

1
daprdocs/content/en/reference/components-reference/supported-middleware/middleware-opa.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: my-policy
namespace: default
spec:
type: middleware.http.opa
version: v1

6
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-apache-kafka.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: kafka-pubsub
namespace: default
spec:
type: pubsub.kafka
version: v1
@ -88,7 +87,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: kafka-pubsub-noauth
namespace: default
spec:
type: pubsub.kafka
version: v1
@ -121,7 +119,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: kafka-pubsub-sasl
namespace: default
spec:
type: pubsub.kafka
version: v1
@ -163,7 +160,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: kafka-pubsub-mtls
namespace: default
spec:
type: pubsub.kafka
version: v1
@ -214,7 +210,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: kafka-pubsub
namespace: default
spec:
type: pubsub.kafka
version: v1
@ -262,7 +257,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: kafka-pubsub
namespace: default
spec:
type: pubsub.kafka
version: v1

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

@ -15,7 +15,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: snssqs-pubsub
namespace: default
spec:
type: pubsub.snssqs
version: v1
@ -136,13 +135,12 @@ spec:
{{% codetab %}}
To run localstack on Kubernetes, you can apply the configuration below. Localstack is then
reachable at the DNS name `http://localstack.default.svc.cluster.local:4566`
(assuming this was applied to the default namespace) and this should be used as the `endpoint`
and this should be used as the `endpoint`
```yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: localstack
namespace: default
spec:
# using the selector, we will expose the running deployments
# this is how Kubernetes knows, that a given service belongs to a deployment

2
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-azure-eventhubs.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: eventhubs-pubsub
namespace: default
spec:
type: pubsub.azure.eventhubs
version: v1
@ -74,7 +73,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: eventhubs-pubsub
namespace: default
spec:
type: pubsub.azure.eventhubs
version: v1

2
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-azure-servicebus.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: servicebus-pubsub
namespace: default
spec:
type: pubsub.azure.servicebus
version: v1
@ -98,7 +97,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: servicebus-pubsub
namespace: default
spec:
type: pubsub.azure.servicebus
version: v1

1
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-gcp-pubsub.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: gcp-pubsub
namespace: default
spec:
type: pubsub.gcp.pubsub
version: v1

1
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-hazelcast.md
View File

@ -15,7 +15,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: hazelcast-pubsub
namespace: default
spec:
type: pubsub.hazelcast
version: v1

1
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-inmemory.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: pubsub
namespace: default
spec:
type: pubsub.in-memory
version: v1

1
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-jetstream.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: jetstream-pubsub
namespace: default
spec:
type: pubsub.jetstream
version: v1

3
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-mqtt.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: mqtt-pubsub
namespace: default
spec:
type: pubsub.mqtt
version: v1
@ -60,7 +59,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: mqtt-pubsub
namespace: default
spec:
type: pubsub.mqtt
version: v1
@ -98,7 +96,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: mqtt-pubsub
namespace: default
spec:
type: pubsub.mqtt
version: v1

1
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-nats-streaming.md
View File

@ -15,7 +15,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: natsstreaming-pubsub
namespace: default
spec:
type: pubsub.natsstreaming
version: v1

1
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: pulsar-pubsub
namespace: default
spec:
type: pubsub.pulsar
version: v1

4
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-rabbitmq.md
View File

@ -14,7 +14,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: rabbitmq-pubsub
namespace: default
spec:
type: pubsub.rabbitmq
version: v1
@ -118,8 +117,7 @@ helm install rabbitmq stable/rabbitmq
Look at the chart output and get the username and password.
This will install RabbitMQ into the `default` namespace.
To interact with RabbitMQ, find the service with: `kubectl get svc rabbitmq`.
This will install RabbitMQ into the `default` namespace. To interact with RabbitMQ, find the service with: `kubectl get svc rabbitmq`.
For example, if installing using the example above, the RabbitMQ server client address would be:

1
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-redis-pubsub.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: redis-pubsub
namespace: default
spec:
type: pubsub.redis
version: v1

1
daprdocs/content/en/reference/components-reference/supported-pubsub/setup-rocketmq.md
View File

@ -15,7 +15,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: rocketmq-pubsub
namespace: default
spec:
type: pubsub.rocketmq
version: v1

1
daprdocs/content/en/reference/components-reference/supported-secret-stores/alicloud-oos-parameter-store.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: alibabacloudparameterstore
namespace: default
spec:
type: secretstores.alicloud.parameterstore
version: v1

1
daprdocs/content/en/reference/components-reference/supported-secret-stores/aws-parameter-store.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: awsparameterstore
namespace: default
spec:
type: secretstores.aws.parameterstore
version: v1

1
daprdocs/content/en/reference/components-reference/supported-secret-stores/aws-secret-manager.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: awssecretmanager
namespace: default
spec:
type: secretstores.aws.secretmanager
version: v1

6
daprdocs/content/en/reference/components-reference/supported-secret-stores/azure-keyvault.md
View File

@ -18,7 +18,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: azurekeyvault
namespace: default
spec:
type: secretstores.azure.keyvault
version: v1
@ -125,7 +124,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: azurekeyvault
namespace: default
spec:
type: secretstores.azure.keyvault
version: v1
@ -147,7 +145,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: azurekeyvault
namespace: default
spec:
type: secretstores.azure.keyvault
version: v1
@ -188,7 +185,6 @@ To use a **client secret**:
kind: Component
metadata:
name: azurekeyvault
namespace: default
spec:
type: secretstores.azure.keyvault
version: v1
@ -234,7 +230,6 @@ To use a **certificate**:
kind: Component
metadata:
name: azurekeyvault
namespace: default
spec:
type: secretstores.azure.keyvault
version: v1
@ -271,7 +266,6 @@ To use **Azure managed identity**:
kind: Component
metadata:
name: azurekeyvault
namespace: default
spec:
type: secretstores.azure.keyvault
version: v1

1
daprdocs/content/en/reference/components-reference/supported-secret-stores/envvar-secret-store.md
View File

@ -22,7 +22,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: envvar-secret-store
namespace: default
spec:
type: secretstores.local.env
version: v1

1
daprdocs/content/en/reference/components-reference/supported-secret-stores/file-secret-store.md
View File

@ -22,7 +22,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: local-secret-store
namespace: default
spec:
type: secretstores.local.file
version: v1

1
daprdocs/content/en/reference/components-reference/supported-secret-stores/gcp-secret-manager.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: gcpsecretmanager
namespace: default
spec:
type: secretstores.gcp.secretmanager
version: v1

1
daprdocs/content/en/reference/components-reference/supported-secret-stores/hashicorp-vault.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: vault
namespace: default
spec:
type: secretstores.hashicorp.vault
version: v1

1
daprdocs/content/en/reference/components-reference/supported-secret-stores/huaweicloud-csms.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: huaweicloudcsms
namespace: default
spec:
type: secretstores.huaweicloud.csms
version: v1

1
daprdocs/content/en/reference/components-reference/supported-secret-stores/kubernetes-secret-store.md
View File

@ -25,7 +25,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: mycustomsecretstore
namespace: default
spec:
type: secretstores.kubernetes
version: v1

1
daprdocs/content/en/reference/components-reference/supported-state-stores/setup-aerospike.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: state.Aerospike
version: v1

2
daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-blobstorage.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: state.azure.blobstorage
version: v1
@ -105,7 +104,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: state.azure.blobstorage
version: v1

1
daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-cosmosdb.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: state.azure.cosmosdb
version: v1

1
daprdocs/content/en/reference/components-reference/supported-state-stores/setup-azure-tablestorage.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: state.azure.tablestorage
version: v1

1
daprdocs/content/en/reference/components-reference/supported-state-stores/setup-cassandra.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: state.cassandra
version: v1

1
daprdocs/content/en/reference/components-reference/supported-state-stores/setup-cockroachdb.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: state.cockroachdb
version: v1

1
daprdocs/content/en/reference/components-reference/supported-state-stores/setup-consul.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: state.consul
version: v1

1
daprdocs/content/en/reference/components-reference/supported-state-stores/setup-couchbase.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: state.couchbase
version: v1

1
daprdocs/content/en/reference/components-reference/supported-state-stores/setup-dynamodb.md
View File

@ -16,7 +16,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: state.aws.dynamodb
version: v1

1
daprdocs/content/en/reference/components-reference/supported-state-stores/setup-firestore.md
View File

@ -17,7 +17,6 @@ apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: state.gcp.firestore
version: v1

Some files were not shown because too many files have changed in this diff Show More