Merge branch 'v1.2' into v1.2

.github/scripts/automerge.py

@@ -0,0 +1,60 @@
+# ------------------------------------------------------------
+# Copyright (c) Microsoft Corporation and Dapr Contributors.
+# Licensed under the MIT License.
+# ------------------------------------------------------------
+
+# This script automerges PRs in Dapr.
+
+import os
+
+from github import Github
+
+
+g = Github(os.getenv("GITHUB_TOKEN"))
+repo = g.get_repo(os.getenv("GITHUB_REPOSITORY"))
+maintainers = [m.strip() for m in os.getenv("MAINTAINERS").split(',')]
+
+def fetch_pulls(mergeable_state):
+    return [pr for pr in repo.get_pulls(state='open', sort='created') \
+        if pr.mergeable_state == mergeable_state and 'automerge' in [l.name for l in pr.labels]]
+
+def is_approved(pr):
+    approvers = [r.user.login for r in pr.get_reviews() if r.state == 'APPROVED' and r.user.login in maintainers]
+    return len([a for a in approvers if repo.get_collaborator_permission(a) in ['admin', 'write']]) > 0
+
+# First, find a PR that can be merged
+pulls = fetch_pulls('clean')
+print(f"Detected {len(pulls)} open pull requests in {repo.name} to be automerged.")
+merged = False
+for pr in pulls:
+    if is_approved(pr):
+        # Merge only one PR per run.
+        print(f"Merging PR {pr.html_url}")
+        try:
+            pr.merge(merge_method='squash')
+            merged = True
+            break
+        except:
+            print(f"Failed to merge PR {pr.html_url}")
+
+if len(pulls) > 0 and not merged:
+    print("No PR was automerged.")
+
+# Now, update all PRs that are behind.
+pulls = fetch_pulls('behind')
+print(f"Detected {len(pulls)} open pull requests in {repo.name} to be updated.")
+for pr in pulls:
+    if is_approved(pr):
+        # Update all PRs since there is no guarantee they will all pass.
+        print(f"Updating PR {pr.html_url}")
+        try:
+            pr.update_branch()
+        except:
+            print(f"Failed to update PR {pr.html_url}")
+
+pulls = fetch_pulls('dirty')
+print(f"Detected {len(pulls)} open pull requests in {repo.name} to be automerged but are in dirty state.")
+for pr in pulls:
+    print(f"PR is in dirty state: {pr.html_url}")
+
+print("Done.")

.github/workflows/dapr-automerge.yml

@@ -0,0 +1,26 @@
+# ------------------------------------------------------------
+# Copyright (c) Microsoft Corporation and Dapr Contributors.
+# Licensed under the MIT License.
+# ------------------------------------------------------------
+
+name: dapr-automerge
+
+on:
+  schedule:
+    - cron: '*/10 * * * *'
+  workflow_dispatch:
+jobs:
+  automerge:
+    if: github.repository_owner == 'dapr'
+    name: Automerge and update PRs.
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@v2
+      - name: Install dependencies
+        run: pip install PyGithub
+      - name: Automerge and update
+        env:
+          MAINTAINERS: AaronCrawfis,orizohar,msfussell
+          GITHUB_TOKEN: ${{ secrets.DAPR_BOT_TOKEN }}
+        run: python ./.github/scripts/automerge.py

OLD/presentations/README.md

@@ -1,20 +0,0 @@
-# Dapr presentations
-
-Here you can find previous Dapr presentations, as well as a PowerPoint & guidance on how you can give your own Dapr presentation.
-
-## Previous Dapr presentations
-
-| Presentation | Recording | Deck |
-|--------------|-----------|------|
-| Ignite 2019: Mark Russinovich Presents the Future of Cloud Native Applications | [Link](https://www.youtube.com/watch?v=LAUDVk8PaCY) | [Link](./PastPresentations/2019IgniteCloudNativeApps.pdf)
-| Azure Community Live: Build microservice applications using DAPR with Mark Fussell | [Link](https://www.youtube.com/watch?v=CgqI7nen-Ng) | N/A
-
-There are other Dapr resources on the [community](https://github.com/dapr/dapr#community) page.
-
-## Giving a Dapr presentation
-
-- Begin by downloading the [Dapr Presentation Deck](./Dapr%20Presentation%20Deck.pptx). This contains slides and diagrams needed to give a Dapr presentation.
-
-- Next, review the [Docs](../README.md) to make sure you understand the [concepts](../concepts) and [best-practices](../best-practices).
-
-- Use the Dapr [quickstarts](https://github.com/dapr/quickstarts) repo and [samples](https://github.com/dapr/samples) repo to show demos of how to use Dapr

daprdocs/content/en/contributing/presentations.md

@@ -0,0 +1,30 @@
+---
+type: docs
+title: "Giving a presentation on Dapr"
+linkTitle: "Presentations"
+weight: 1500
+description: How to give a presentation on Dapr and examples
+---
+
+We welcome community members giving presentations on Dapr and spreading the word about all the awesome Dapr features! We offer a template PowerPoint file to get started.
+
+{{< button text="Download the Dapr Presentation Deck" link="/presentations/dapr-slidedeck.zip" >}}
+
+## Giving a Dapr presentation
+
+- Begin by downloading the [Dapr Presentation Deck](/presentations/dapr-slidedeck.zip). This contains slides and diagrams needed to give a Dapr presentation.
+- Next, review the docs to make sure you understand the [concepts]({{< ref concepts >}}).
+- Use the Dapr [quickstarts](https://github.com/dapr/quickstarts) repo and [samples](https://github.com/dapr/samples) repo to show demos of how to use Dapr.
+
+## Previous Dapr presentations
+
+| Presentation | Recording | Deck |
+|--------------|-----------|------|
+| Ignite 2019: Mark Russinovich Presents the Future of Cloud Native Applications | [Link](https://www.youtube.com/watch?v=LAUDVk8PaCY) | [Link](/presentations/2019IgniteCloudNativeApps.pdf)
+| Azure Community Live: Build microservice applications using DAPR with Mark Fussell | [Link](https://www.youtube.com/watch?v=CgqI7nen-Ng) | N/A
+| Ready 2020: Mark Russinovich Presents Cloud Native Applications | [Link](https://youtu.be/eJCu6a-x9uo?t=1614) | [Link](/presentations/2020ReadyCloudNativeApps.pdf)
+| Ignite 2021: Mark Russinovich Presents Dapr v1.0 Release | [Link](https://youtu.be/69PrhWQorEM?t=3789) | N/A
+
+## Additional resources
+
+There are other Dapr resources on the [community](https://github.com/dapr/community) repo.

daprdocs/content/en/developing-applications/building-blocks/actors/actors-overview.md

@@ -77,7 +77,7 @@ POST/GET/PUT/DELETE http://localhost:3500/v1.0/actors/<actorType>/<actorId>/<met
 
 You can provide any data for the actor method in the request body, and the response for the request would be in the response body which is the data from actor call.
 
-Refer to [Dapr Actor Features]({{< ref actors-overview.md >}}) for more details.
+Refer to [Dapr Actor Features]({{< ref howto-actors.md >}}) for more details.
 
 ### Concurrency
 

daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-overview.md

@@ -100,6 +100,9 @@ Dapr can set a timeout message on a per message basis, meaning that if the messa
 
 - Note: Message TTL can also be set for a given queue at the time of component creation. Look at the specific characteristic of the component that you are using.
 
+### Communication with applications not using Dapr and CloudEvents
+For scenarios where one application uses Dapr but another doesn't, CloudEvent wrapping can be disabled for a publisher or subscriber. This allows partial adoption of Dapr pubsub in applications that cannot adopt Dapr all at once. For more information read [how to use pubsub without CloudEvent]({{< ref pubsub-raw.md >}}).
+
 ### Publish/Subscribe API
 
 The publish/subscribe API is located in the [API reference]({{< ref pubsub_api.md >}}).
@@ -112,5 +115,6 @@ The publish/subscribe API is located in the [API reference]({{< ref pubsub_api.m
 * Try out the [Pub/Sub quickstart sample](https://github.com/dapr/quickstarts/tree/master/pub-sub)
 * Learn about [topic scoping]({{< ref pubsub-scopes.md >}})
 * Learn about [message time-to-live (TTL)]({{< ref pubsub-message-ttl.md >}})
+* Learn about [pubsub without CloudEvent]({{< ref pubsub-raw.md >}})
 * List of [pub/sub components]({{< ref supported-pubsub.md >}})
 * Read the [pub/sub API reference]({{< ref pubsub_api.md >}})

daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-raw.md

@@ -0,0 +1,160 @@
+---
+type: docs
+title: "Pub/Sub without CloudEvents"
+linkTitle: "Pub/Sub without CloudEvents"
+weight: 7000
+description: "Use Pub/Sub without CloudEvents." 
+---
+
+## Introduction
+
+Dapr uses CloudEvents to provide additional context to the event payload, enabling features like:
+* Tracing
+* Deduplication by message Id
+* Content-type for proper deserialization of event's data
+
+For more information about CloudEvents, read the [CloudEvents specification](https://github.com/cloudevents/spec).
+
+When adding Dapr to your application, some services may still need to communicate via raw pub/sub messages not encapsulated in CloudEvents. This may be for compatibility reasons, or because some apps are not using Dapr. Dapr enables apps to publish and subscribe to raw events that are not wrapped in a CloudEvent.
+
+{{% alert title="Warning" color="warning" %}}
+Not using CloudEvents disables support for tracing, event deduplication per messageId, content-type metadata, and any other features built using the CloudEvent schema.
+{{% /alert %}}
+
+## Publishing raw messages
+
+Dapr apps are able to publish raw events to pub/sub topics without CloudEvent encapsulation, for compatibility with non-Dapr apps.
+
+<img src="/images/pubsub_publish_raw.png" alt="Diagram showing how to publish with Dapr when subscriber does not use Dapr or CloudEvent" width=1000>
+
+To disable CloudEvent wrapping, set the `rawPayload` metadata to `true` as part of the publishing request. This allows subscribers to receive these messages without having to parse the CloudEvent schema.
+
+{{< tabs curl "Python SDK" "PHP SDK">}}
+
+{{% codetab %}}
+```bash
+curl -X "POST" http://localhost:3500/v1.0/publish/pubsub/TOPIC_A?metadata.rawPayload=true -H "Content-Type: application/json" -d '{"order-number": "345"}'
+```
+{{% /codetab %}}
+
+{{% codetab %}}
+```python
+from dapr.clients import DaprClient
+
+with DaprClient() as d:
+    req_data = {
+        'order-number': '345'
+    }
+    # Create a typed message with content type and body
+    resp = d.publish_event(
+        pubsub_name='pubsub',
+        topic='TOPIC_A',
+        data=json.dumps(req_data),
+        metadata=(
+                     ('rawPayload', 'true')
+                 )
+    )
+    # Print the request
+    print(req_data, flush=True)
+```
+{{% /codetab %}}
+
+{{% codetab %}}
+
+```php
+<?php
+
+require_once __DIR__.'/vendor/autoload.php';
+
+$app = \Dapr\App::create();
+$app->run(function(\DI\FactoryInterface $factory) {
+    $publisher = $factory->make(\Dapr\PubSub\Publish::class, ['pubsub' => 'pubsub']);
+    $publisher->topic('TOPIC_A')->publish('data', ['rawPayload' => 'true']);
+});
+```
+
+{{% /codetab %}}
+
+{{< /tabs >}}
+
+## Subscribing to raw messages
+
+Dapr apps are also able to subscribe to raw events coming from existing pub/sub topics that do not use CloudEvent encapsulation.
+
+<img src="/images/pubsub_subscribe_raw.png" alt="Diagram showing how to subscribe with Dapr when publisher does not use Dapr or CloudEvent" width=1000>
+
+
+### Programmatically subscribe to raw events 
+
+When subscribing programmatically, add the additional metadata entry for `rawPayload` so the Dapr sidecar automatically wraps the payloads into a CloudEvent that is compatible with current Dapr SDKs.
+
+{{< tabs "Python" "PHP SDK" >}}
+
+{{% codetab %}}
+
+```python
+import flask
+from flask import request, jsonify
+from flask_cors import CORS
+import json
+import sys
+
+app = flask.Flask(__name__)
+CORS(app)
+
+@app.route('/dapr/subscribe', methods=['GET'])
+def subscribe():
+    subscriptions = [{'pubsubname': 'pubsub',
+                      'topic': 'deathStarStatus',
+                      'route': 'dsstatus',
+                      'metadata': {
+                          'rawPayload': 'true',
+                      } }]
+    return jsonify(subscriptions)
+
+@app.route('/dsstatus', methods=['POST'])
+def ds_subscriber():
+    print(request.json, flush=True)
+    return json.dumps({'success':True}), 200, {'ContentType':'application/json'}
+
+app.run()
+```
+
+{{% /codetab %}}
+{{% codetab %}}
+
+```php
+<?php
+
+require_once __DIR__.'/vendor/autoload.php';
+
+$app = \Dapr\App::create(configure: fn(\DI\ContainerBuilder $builder) => $builder->addDefinitions(['dapr.subscriptions' => [
+    new \Dapr\PubSub\Subscription(pubsubname: 'pubsub', topic: 'deathStarStatus', route: '/dsstatus', metadata: [ 'rawPayload' => 'true'] ),
+]]));
+
+$app->post('/dsstatus', function(
+    #[\Dapr\Attributes\FromBody]
+    \Dapr\PubSub\CloudEvent $cloudEvent,
+    \Psr\Log\LoggerInterface $logger
+    ) {
+        $logger->alert('Received event: {event}', ['event' => $cloudEvent]);
+        return ['status' => 'SUCCESS'];
+    }
+);
+
+$app->start();
+```
+{{% /codetab %}}
+
+{{< /tabs >}}
+
+
+## Declaratively subscribe to raw events
+
+Subscription Custom Resources Definitions (CRDs) do not currently contain metadata attributes ([issue #3225](https://github.com/dapr/dapr/issues/3225)). At this time subscribing to raw events can only be done through programmatic subscriptions.
+
+## Related links
+
+- Learn more about [how to publish and subscribe]({{< ref howto-publish-subscribe.md >}})
+- List of [pub/sub components]({{< ref supported-pubsub >}})
+- Read the [API reference]({{< ref pubsub_api.md >}})

daprdocs/content/en/developing-applications/integrations/open-service-mesh.md

@@ -0,0 +1,29 @@
+---
+type: docs
+title: "Running Dapr and Open Service Mesh together"
+linkTitle: "Open Service Mesh"
+weight: 4000
+description: "Learn how to run both Open Service Mesh and Dapr on the same Kubernetes cluster"
+---
+
+## Overview
+
+[Open Service Mesh (OSM)](https://openservicemesh.io/) is a lightweight, extensible, cloud native service mesh that allows users to uniformly manage, secure, and get out-of-the-box observability features for highly dynamic microservice environments.
+
+{{< button text="Learn more" link="https://openservicemesh.io/" >}}
+
+## Dapr integration
+
+Users are able to leverage both OSM SMI traffic policies and Dapr capabilities on the same Kubernetes cluster. Visit [this guide](https://docs.openservicemesh.io/docs/integrations/demo_dapr/) to get started.
+
+{{< button text="Deploy OSM and Dapr" link="https://docs.openservicemesh.io/docs/integrations/demo_dapr/" >}}
+
+## Example
+
+Watch the OSM team present the OSM and Dapr integration in the 05/18/2021 community call:
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/LSYyTL0nS8Y?start=1916" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+## Additional resources
+
+- [Dapr and service meshes]({{< ref service-mesh.md >}})

daprdocs/content/en/developing-applications/integrations/workflows.md

@@ -6,4 +6,224 @@ description: "Learn how to build workflows using Dapr Workflows and Logic Apps"
 weight: 4000
 ---
 
-To enable developers to easily build workflow applications that use Dapr’s capabilities including diagnostics and multi-language support, you can use Dapr workflows. Dapr integrates with workflow engines such as Logic Apps runtime.  For more information read [cloud-native workflows using Dapr and Logic Apps](https://cloudblogs.microsoft.com/opensource/2020/05/26/announcing-cloud-native-workflows-dapr-logic-apps/) and visit the [Dapr workflow](https://github.com/dapr/workflows) repo to try out the samples.
+Dapr Workflows is a lightweight host that allows developers to run cloud-native workflows locally, on-premises or any cloud environment using the [Azure Logic Apps](https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-overview) workflow engine and Dapr.
+
+## Benefits
+
+By using a workflow engine, business logic can be defined in a declarative, no-code fashion so application code doesn't need to change when a workflow changes. Dapr Workflows allows you to use workflows in a distributed application along with these added benefits:
+
+- **Run workflows anywhere**: on your local machine, on-premises, on Kubernetes or in the cloud
+- **Built-in observability**: tracing, metrics and mTLS through Dapr
+- **gRPC and HTTP endpoints** for your workflows
+- Kick off workflows based on **Dapr bindings** events
+- Orchestrate complex workflows by **calling back to Dapr** to save state, publish a message and more
+
+<img src="/images/workflows-diagram.png" width=500 alt="Diagram of Dapr Workflows">
+
+## How it works
+
+Dapr Workflows hosts a gRPC server that implements the Dapr Client API.
+
+This allows users to start workflows using gRPC and HTTP endpoints through Dapr, or start a workflow asynchronously using Dapr bindings.
+Once a workflow request comes in, Dapr Workflows uses the Logic Apps SDK to execute the workflow.
+
+## Supported workflow features
+
+### Supported actions and triggers
+
+- [HTTP](https://docs.microsoft.com/en-us/azure/connectors/connectors-native-http)
+- [Schedule](https://docs.microsoft.com/en-us/azure/logic-apps/concepts-schedule-automated-recurring-tasks-workflows)
+- [Request / Response](https://docs.microsoft.com/en-us/azure/connectors/connectors-native-reqres)
+
+### Supported control workflows
+
+- [All control workflows](https://docs.microsoft.com/en-us/azure/connectors/apis-list#control-workflow)
+
+### Supported data manipulation
+
+- [All data operations](https://docs.microsoft.com/en-us/azure/connectors/apis-list#manage-or-manipulate-data)
+
+### Not supported
+
+- [Managed connectors](https://docs.microsoft.com/en-us/azure/connectors/apis-list#managed-connectors)
+
+## Example
+
+Dapr Workflows can be used as the orchestrator for many otherwise complex activities. For example, invoking an external endpoint, saving the data to a state store, publishing the result to a different app or invoking a binding can all be done by calling back into Dapr from the workflow itself.
+
+This is due to the fact Dapr runs as a sidecar next to the workflow host just as if it was any other app.
+
+Examine [workflow2.json](/code/workflow.json) as an example of a workflow that does the following:
+
+1. Calls into Azure Functions to get a JSON response
+2. Saves the result to a Dapr state store
+3. Sends the result to a Dapr binding
+4. Returns the result to the caller
+
+Since Dapr supports many pluggable state stores and bindings, the workflow becomes portable between different environments (cloud, edge or on-premises) without the user changing the code - *because there is no code involved*.
+
+## Get started
+
+Prerequisites:
+
+1. Install the [Dapr CLI]({{< ref install-dapr-cli.md >}})
+2. [Azure blob storage account](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-create-account-block-blob?tabs=azure-portal)
+
+### Self-hosted
+
+1. Make sure you have the Dapr runtime initialized:
+
+    ```bash
+    dapr init
+    ```
+
+1. Set up the environment variables containing the Azure Storage Account credentials:
+
+   {{< tabs Windows "macOS/Linux" >}}
+   
+   {{% codetab %}}
+   ```bash
+   export STORAGE_ACCOUNT_KEY=<YOUR-STORAGE-ACCOUNT-KEY>
+   export STORAGE_ACCOUNT_NAME=<YOUR-STORAGE-ACCOUNT-NAME>
+   ```
+   {{% /codetab %}}
+   
+   {{% codetab %}}
+   ```bash
+   set STORAGE_ACCOUNT_KEY=<YOUR-STORAGE-ACCOUNT-KEY>
+   set STORAGE_ACCOUNT_NAME=<YOUR-STORAGE-ACCOUNT-NAME>
+   ```
+   {{% /codetab %}}
+   
+   {{< /tabs >}}
+
+1. Move to the workflows directory and run the sample runtime:
+
+   ```bash
+   cd src/Dapr.Workflows
+   
+   dapr run --app-id workflows --protocol grpc --port 3500 --app-port    50003 -- dotnet run --workflows-path ../../samples
+   ```
+
+1. Invoke a workflow:
+
+   ```bash
+   curl http://localhost:3500/v1.0/invoke/workflows/method/workflow1
+   
+   {"value":"Hello from Logic App workflow running with    Dapr!"}                                                                                      
+   ```
+
+### Kubernetes
+
+1. Make sure you have a running Kubernetes cluster and `kubectl` in your path.
+
+1. Once you have the Dapr CLI installed, run:
+
+   ```bash
+   dapr init --kubernetes
+   ```
+
+1. Wait until the Dapr pods have the status `Running`.
+
+1. Create a Config Map for the workflow:
+
+   ```bash
+   kubectl create configmap workflows --from-file ./samples/workflow1.   json
+   ```
+
+1. Create a secret containing the Azure Storage Account credentials. Replace the account name and key values below with the actual credentials:
+
+   ```bash
+   kubectl create secret generic dapr-workflows    --from-literal=accountName=<YOUR-STORAGE-ACCOUNT-NAME>    --from-literal=accountKey=<YOUR-STORAGE-ACCOUNT-KEY>
+   ```
+
+1. Deploy Dapr Worfklows:
+
+   ```bash
+   kubectl apply -f deploy/deploy.yaml
+   ```
+
+1. Create a port-forward to the dapr workflows container:
+
+   ```bash
+   kubectl port-forward deploy/dapr-workflows-host 3500:3500
+   ```
+
+1. Invoke logic apps through Dapr:
+
+   ```bash
+   curl http://localhost:3500/v1.0/invoke/workflows/method/workflow1
+   
+   {"value":"Hello from Logic App workflow running with Dapr!"}
+   ```
+
+## Invoking workflows using Dapr bindings
+
+1. First, create any [Dapr binding]({{< ref components-reference >}}) of your choice. See [this]({{< ref howto-triggers >}}) How-To tutorial.
+
+   In order for Dapr Workflows to be able to start a workflow from a Dapr binding event, simply name the binding with the name of the workflow you want it to trigger.
+
+   Here's an example of a Kafka binding that will trigger a workflow named `workflow1`:
+
+   ```yaml
+   apiVersion: dapr.io/v1alpha1
+   kind: Component
+   metadata:
+     name: workflow1
+   spec:
+     type: bindings.kafka
+     metadata:
+     - name: topics
+       value: topic1
+     - name: brokers
+       value: localhost:9092
+     - name: consumerGroup
+       value: group1
+     - name: authRequired
+       value: "false"
+   ```
+
+1. Next, apply the Dapr component:
+
+   {{< tabs Self-hosted Kubernetes >}}
+   
+   {{% codetab %}}
+   Place the binding yaml file above in a `components` directory at the    root of your application.
+   {{% /codetab %}}
+   
+   {{% codetab %}}
+   ```bash
+   kubectl apply -f my_binding.yaml
+   ```
+   {{% /codetab %}}
+   
+   {{< /tabs >}}
+
+1. Once an event is sent to the bindings component, check the logs Dapr Workflows to see the output.
+
+   {{< tabs Self-hosted Kubernetes >}}
+   
+   {{% codetab %}}
+   In standalone mode, the output will be printed to the local terminal.
+   {{% /codetab %}}
+   
+   {{% codetab %}}
+   On Kubernetes, run the following command:
+   
+   ```bash
+   kubectl logs -l app=dapr-workflows-host -c host
+   ```
+   {{% /codetab %}}
+   
+   {{< /tabs >}}
+
+## Example
+
+Watch an example from the Dapr community call:
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/7fP-0Ixmi-w?start=116" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+## Additional resources
+
+- [Blog announcement](https://cloudblogs.microsoft.com/opensource/2020/05/26/announcing-cloud-native-workflows-dapr-logic-apps/)
+- [Repo](https://github.com/dapr/workflows)

daprdocs/content/en/developing-applications/sdks/_index.md

@@ -37,8 +37,8 @@ The Dapr SDKs are the easiest way for you to get Dapr into your application. Cho
 | [Go](https://github.com/dapr/go-sdk) | Stable | ✔ | ✔ |  |
 | [PHP]({{< ref php >}}) | Stable | ✔ | ✔ | ✔ |
 | [C++](https://github.com/dapr/cpp-sdk) | In development | ✔ | |
-| [Rust]() | In development | ✔ | |  |
+| [Rust](https://github.com/dapr/rust-sdk) | In development | ✔ | |  |
-| [Javascript]() | In development| ✔ | |
+| [Javascript](https://github.com/dapr/js-sdk) | In development| ✔ | |
 
 ## Further reading
 

daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md

@@ -61,7 +61,7 @@ The CPU and memory limits above account for the fact that Dapr is intended to a
 
 When deploying Dapr in a production-ready configuration, it's recommended to deploy with a highly available (HA) configuration of the control plane, which creates 3 replicas of each control plane pod in the dapr-system namespace. This configuration allows for the Dapr control plane to survive node failures and other outages.
 
-HA mode can be enabled with both the [Dapr CLI]({{< ref "kubernetes-deploy.md#install-in-highly-available-mode" >}} and with [Helm charts]({{< ref "kubernetes-deploy.md#add-and-install-dapr-helm-chart" >}}).
+HA mode can be enabled with both the [Dapr CLI]({{< ref "kubernetes-deploy.md#install-in-highly-available-mode" >}}) and with [Helm charts]({{< ref "kubernetes-deploy.md#add-and-install-dapr-helm-chart" >}}).
 
 ## Deploying Dapr with Helm
 

daprdocs/content/en/operations/hosting/self-hosted/self-hosted-no-docker.md

@@ -29,11 +29,11 @@ See [this sample](https://github.com/dapr/samples/tree/master/hello-dapr-slim) f
 
 ## Enabling state management or pub/sub
 
-See configuring Redis in self hosted mode [without docker](https://redis.io/topics/quickstart) to enable a local state store or pub/sub broker for messaging. 
+See configuring Redis in self-hosted mode [without docker](https://redis.io/topics/quickstart) to enable a local state store or pub/sub broker for messaging. 
 
 ## Enabling actors
 
-The placement service must be run locally to enable actor placement. Also a [transactional state store](#Enabling-state-management-or-pub/sub) must be enabled for actors. 
+The placement service must be run locally to enable actor placement. Also, a [transactional state store that supports ETags]({{< ref "supported-state-stores.md" >}}) must be enabled to use actors, for example, [Redis configured in self-hosted mode](https://redis.io/topics/quickstart).
 
 By default for Linux/MacOS the `placement` binary is installed in `/$HOME/.dapr/bin` or for Windows at `%USERPROFILE%\.dapr\bin`.
 

daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md

@@ -20,10 +20,10 @@ Jaeger image published to DockerHub:
 
 ```bash
 docker run -d --name jaeger \
-  -e COLLECTOR_ZIPKIN_HTTP_PORT=9412 \
+  -e COLLECTOR_ZIPKIN_HOST_PORT=:9412 \
   -p 16686:16686 \
   -p 9412:9412 \
-  jaegertracing/all-in-one:1.21
+  jaegertracing/all-in-one:1.22
 ```
 
 
@@ -74,7 +74,7 @@ spec:
   ingress:
     enabled: false
   allInOne:
-    image: jaegertracing/all-in-one:1.13
+    image: jaegertracing/all-in-one:1.22
     options:
       query:
         base-path: /jaeger

daprdocs/content/en/operations/security/mtls.md

@@ -91,23 +91,54 @@ kubectl logs --selector=app=dapr-sentry --namespace <DAPR_NAMESPACE>
 
 ### Bringing your own certificates
 
-Using Helm, you can provide the PEM encoded root cert, issuer cert and private key that will be populated into the Kubernetes secret.
+Using Helm, you can provide the PEM encoded root cert, issuer cert and private key that will be populated into the Kubernetes secret used by Sentry.
 
-*Note: This example uses the step tool to create the certificates. You can install step tool from [here](https://smallstep.com/docs/getting-started/). Windows binaries available [here](https://github.com/smallstep/cli/releases)*
+_Note: This example uses the OpenSSL command line tool, this is a widely distributed package, easily installed on Linux via the package manager. On Windows OpenSSL can be installed [using chocolatey](https://community.chocolatey.org/packages/openssl). On MacOS it can be installed using brew `brew install openssl`_
 
-Create the root certificate:
+Create config files for generating the certificates, this is necessary for generating v3 certificates with the SAN (Subject Alt Name) extension fields. First save the following to a file named `root.conf`:
 
-```
+```ini
-step certificate create cluster.local ca.crt ca.key --profile root-ca --no-password --insecure
+[req]
+distinguished_name = req_distinguished_name
+x509_extensions = v3_req
+prompt = no
+[req_distinguished_name]
+C = US
+ST = VA
+L = Daprville
+O = dapr.io/sentry
+OU = dapr.io/sentry
+CN = cluster.local
+[v3_req]
+basicConstraints = critical, CA:true
+keyUsage = critical, digitalSignature, cRLSign, keyCertSign
+extendedKeyUsage = serverAuth, clientAuth
+subjectAltName = @alt_names
+[alt_names]
+DNS.1 = cluster.local
 ```
 
-Create the issuer certificate:
+Repeat this for `issuer.conf`, paste the same contents into the file, but add `pathlen:0` to the end of the basicConstraints line, as shown below:
 
-```
+```ini
-step certificate create cluster.local issuer.crt issuer.key --ca ca.crt --ca-key ca.key --profile intermediate-ca --not-after 8760h --no-password --insecure
+basicConstraints = critical, CA:true, pathlen:0
 ```
 
-This creates the root and issuer certs and keys.
+Run the following to generate the root cert and key
+
+```bash
+openssl ecparam -genkey -name prime256v1 | openssl ec -out root.key
+openssl req -new -nodes -sha256 -key root.key -out root.csr -config root.conf -extensions v3_req
+openssl x509 -req -sha256 -days 365 -in root.csr -signkey root.key -outform PEM -out root.pem -extfile root.conf -extensions v3_req
+```
+
+Next run the following to generate the issuer cert and key:
+
+```bash
+openssl ecparam -genkey -name prime256v1 | openssl ec -out issuer.key
+openssl req -new -sha256 -key issuer.key -out issuer.csr -config issuer.conf -extensions v3_req
+openssl x509 -req -in issuer.csr -CA root.pem -CAkey root.key -CAcreateserial -outform PEM -out issuer.pem -days 365 -sha256 -extfile issuer.conf -extensions v3_req
+```
 
 Install Helm and pass the root cert, issuer cert and issuer key to Sentry via configuration:
 
@@ -115,9 +146,9 @@ Install Helm and pass the root cert, issuer cert and issuer key to Sentry via co
 kubectl create ns dapr-system
 
 helm install \
-  --set-file dapr_sentry.tls.issuer.certPEM=issuer.crt \
+  --set-file dapr_sentry.tls.issuer.certPEM=issuer.pem \
   --set-file dapr_sentry.tls.issuer.keyPEM=issuer.key \
-  --set-file dapr_sentry.tls.root.certPEM=ca.crt \
+  --set-file dapr_sentry.tls.root.certPEM=root.pem \
   --namespace dapr-system \
   dapr \
   dapr/dapr

daprdocs/content/en/operations/support/support-release-policy.md

@@ -61,11 +61,10 @@ Deprecations appear in release notes under a section named “Deprecations”, w
 
 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.
 
-Here is an example, using a hypothetical 1.1.0 as the deprecation announcement release.
+### Announced deprecations
-
+| Feature               |   Deprecation announcement   | Removal       |
-| Feature               |   Deprecation announcement   | Deprecation       |
 |-----------------------|-----------------------|------------------------- |
-| Feature X             |                 1.1.0 |                    1.3.0 |
+| GET /v1.0/shutdown API (Users should use [POST API]({{< ref kubernetes-job.md >}}) instead)             |                 1.2.0 |                    1.4.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 >}})

daprdocs/content/en/operations/support/support-versioning.md

@@ -28,7 +28,7 @@ Dapr has the following versioning schemes:
 
 Note that the Dapr APIs,  binaries releases (runtime, CLI, SDKs) and components are all independent from one another.
 
-## Dapr API 
+## Dapr HTTP API
 The Dapr HTTP API is versioned according to these [REST API guidelines](https://github.com/microsoft/api-guidelines/blob/vNext/Guidelines.md#71-url-structure).
 
 Based to the these guidelines;

daprdocs/content/en/reference/api/pubsub_api.md

@@ -60,6 +60,7 @@ Metadata can be sent via query parameters in the request's URL. It must be prefi
 Parameter | Description
 --------- | -----------
 metadata.ttlInSeconds | the number of seconds for the message to expire as [described here]({{< ref pubsub-message-ttl.md >}})
+metadata.rawPayload | boolean to determine if Dapr should publish the event without wrapping it as CloudEvent as [described here]({{< ref pubsub-raw.md >}})
 
 > Additional metadata parameters are available based on each pubsub component.
 
@@ -92,13 +93,24 @@ Example:
   {
     "pubsubname": "pubsub",
     "topic": "newOrder",
-    "route": "/orders"
+    "route": "/orders",
+    "metadata": {
+      "rawPayload": "true",
+    }
   }
 ]
 ```
 
 > Note, all subscription parameters are case-sensitive.
 
+#### Metadata
+
+Optionally, metadata can be sent via the request body.
+
+Parameter | Description
+--------- | -----------
+rawPayload | boolean to subscribe to events that do not comply with CloudEvent specification, as [described here]({{< ref pubsub-raw.md >}})
+
 ### Provide route(s) for Dapr to deliver topic events
 
 In order to deliver topic events, a `POST` call will be made to user code with the route specified in the subscription response.

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

@@ -69,7 +69,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr
 | disableEntityManagement | N | When set to `"true"`, topics and subscriptions do not get created automatically. Default: `"false"` | `"true"`, `"false"`
 
 ## Create a GCP Pub/Sub
-You can use either "explicit" or "implicit" credentials to configure access to your GCP pubsub instance. If using explicit, most fields are required. Implicit relies on dapr running under a Kubernetes service acccount (KSA) mapped to a Google service account (GSA) which has the necessary permissions to access pubsub. In implicit mode, only the `projectId` attribute is needed, all other are optional.
+You can use either "explicit" or "implicit" credentials to configure access to your GCP pubsub instance. If using explicit, most fields are required. Implicit relies on dapr running under a Kubernetes service account (KSA) mapped to a Google service account (GSA) which has the necessary permissions to access pubsub. In implicit mode, only the `projectId` attribute is needed, all other are optional.
 
 Follow the instructions [here](https://cloud.google.com/pubsub/docs/quickstart-console) on setting up Google Cloud Pub/Sub system.
 

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

@@ -48,7 +48,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr
 |--------------------|:--------:|---------|---------|
 | host               | Y        | Connection-string for the rabbitmq host  | `amqp://user:pass@localhost:5672`
 | durable            | N        | Whether or not to use [durable](https://www.rabbitmq.com/queues.html#durability) queues. Defaults to `"false"`  | `"true"`, `"false"`
-| deletedWhenUnused  | N        | Whether or not the queue sohuld be configured to [auto-delete](https://www.rabbitmq.com/queues.html) Defaults to `"false"` | `"true"`, `"false"`
+| deletedWhenUnused  | N        | Whether or not the queue sohuld be configured to [auto-delete](https://www.rabbitmq.com/queues.html) Defaults to `"true"` | `"true"`, `"false"`
 | autoAck  | N        | Whether or not the queue consumer should [auto-ack](https://www.rabbitmq.com/confirms.html) messages. Defaults to `"false"` | `"true"`, `"false"`
 | deliveryMode  | N        | Persistence mode when publishing messages. Defaults to `"0"`. RabbitMQ treats `"2"` as persistent, all other numbers as non-persistent | `"0"`, `"2"`
 | requeueInFailure  | N        | Whether or not to requeue when sending a [negative acknolwedgement](https://www.rabbitmq.com/nack.html) in case of a failure. Defaults to `"false"` | `"true"`, `"false"`

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

@@ -57,6 +57,7 @@ The above example uses secrets as plain strings. It is recommended to use a loca
 | vaultTokenMountPath | Y | Path to file containing token | `"path/to/file"` |
 | vaultToken | Y | [Token](https://learn.hashicorp.com/tutorials/vault/tokens) for authentication within Vault.  | `"tokenValue"` |
 | vaultKVPrefix | N | The prefix in vault. Defautls to `"dapr"` | `"dapr"`, `"myprefix"` |
+
 ## Setup Hashicorp Vault instance
 
 {{< tabs "Self-Hosted" "Kubernetes" >}}

daprdocs/package-lock.json

@@ -142,15 +142,14 @@
       }
     },
     "node_modules/autoprefixer": {
-      "version": "10.2.5",
+      "version": "10.2.6",
-      "resolved": "https://registry.npmjs.org/autoprefixer/-/autoprefixer-10.2.5.tgz",
+      "resolved": "https://registry.npmjs.org/autoprefixer/-/autoprefixer-10.2.6.tgz",
-      "integrity": "sha512-7H4AJZXvSsn62SqZyJCP+1AWwOuoYpUfK6ot9vm0e87XD6mT8lDywc9D9OTJPMULyGcvmIxzTAMeG2Cc+YX+fA==",
+      "integrity": "sha512-8lChSmdU6dCNMCQopIf4Pe5kipkAGj/fvTMslCsih0uHpOrXOPUEVOmYMMqmw3cekQkSD7EhIeuYl5y0BLdKqg==",
-      "dev": true,
       "dependencies": {
-        "browserslist": "^4.16.3",
+        "browserslist": "^4.16.6",
-        "caniuse-lite": "^1.0.30001196",
+        "caniuse-lite": "^1.0.30001230",
         "colorette": "^1.2.2",
-        "fraction.js": "^4.0.13",
+        "fraction.js": "^4.1.1",
         "normalize-range": "^0.1.2",
         "postcss-value-parser": "^4.1.0"
       },
@@ -193,7 +192,6 @@
       "version": "4.16.6",
       "resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.16.6.tgz",
       "integrity": "sha512-Wspk/PqO+4W9qp5iUTJsa1B/QrYn1keNCcEP5OvP7WBwT4KaDly0uONYmC6Xa3Z5IqnUgS0KcgLYu1l74x0ZXQ==",
-      "dev": true,
       "dependencies": {
         "caniuse-lite": "^1.0.30001219",
         "colorette": "^1.2.2",
@@ -222,10 +220,9 @@
       }
     },
     "node_modules/caniuse-lite": {
-      "version": "1.0.30001228",
+      "version": "1.0.30001230",
-      "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001228.tgz",
+      "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001230.tgz",
-      "integrity": "sha512-QQmLOGJ3DEgokHbMSA8cj2a+geXqmnpyOFT0lhQV6P3/YOJvGDEwoedcwxEQ30gJIwIIunHIicunJ2rzK5gB2A==",
+      "integrity": "sha512-5yBd5nWCBS+jWKTcHOzXwo5xzcj4ePE/yjtkZyUV1BTUmrBaA9MRGC+e7mxnqXSA90CmCA8L3eKLaSUkt099IQ==",
-      "dev": true,
       "funding": {
         "type": "opencollective",
         "url": "https://opencollective.com/browserslist"
@@ -335,10 +332,9 @@
       }
     },
     "node_modules/electron-to-chromium": {
-      "version": "1.3.736",
+      "version": "1.3.739",
-      "resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.3.736.tgz",
+      "resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.3.739.tgz",
-      "integrity": "sha512-DY8dA7gR51MSo66DqitEQoUMQ0Z+A2DSXFi7tK304bdTVqczCAfUuyQw6Wdg8hIoo5zIxkU1L24RQtUce1Ioig==",
+      "integrity": "sha512-+LPJVRsN7hGZ9EIUUiWCpO7l4E3qBYHNadazlucBfsXBbccDFNKUBAgzE68FnkWGJPwD/AfKhSzL+G+Iqb8A4A=="
-      "dev": true
     },
     "node_modules/emoji-regex": {
       "version": "8.0.0",
@@ -359,7 +355,6 @@
       "version": "3.1.1",
       "resolved": "https://registry.npmjs.org/escalade/-/escalade-3.1.1.tgz",
       "integrity": "sha512-k0er2gUkLf8O0zKJiAhmkTnJlTvINGv7ygDNPbeIsX/TJjGJZHuh9B2UxbsaEkmlEo9MfhrSzmhIlhRlI2GXnw==",
-      "dev": true,
       "engines": {
         "node": ">=6"
       }
@@ -415,7 +410,6 @@
       "version": "4.1.1",
       "resolved": "https://registry.npmjs.org/fraction.js/-/fraction.js-4.1.1.tgz",
       "integrity": "sha512-MHOhvvxHTfRFpF1geTK9czMIZ6xclsEor2wkIGYYq+PxcQqT7vStJqjhe6S1TenZrMZzo+wlqOufBDVepUEgPg==",
-      "dev": true,
       "engines": {
         "node": "*"
       },
@@ -723,8 +717,7 @@
     "node_modules/node-releases": {
       "version": "1.1.72",
       "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-1.1.72.tgz",
-      "integrity": "sha512-LLUo+PpH3dU6XizX3iVoubUNheF/owjXCZZ5yACDxNnPtgFuludV1ZL3ayK1kVep42Rmm0+R9/Y60NQbZ2bifw==",
+      "integrity": "sha512-LLUo+PpH3dU6XizX3iVoubUNheF/owjXCZZ5yACDxNnPtgFuludV1ZL3ayK1kVep42Rmm0+R9/Y60NQbZ2bifw=="
-      "dev": true
     },
     "node_modules/normalize-path": {
       "version": "3.0.0",
@@ -739,7 +732,6 @@
       "version": "0.1.2",
       "resolved": "https://registry.npmjs.org/normalize-range/-/normalize-range-0.1.2.tgz",
       "integrity": "sha1-LRDAa9/TEuqXd2laTShDlFa3WUI=",
-      "dev": true,
       "engines": {
         "node": ">=0.10.0"
       }
@@ -956,8 +948,7 @@
     "node_modules/postcss-value-parser": {
       "version": "4.1.0",
       "resolved": "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.1.0.tgz",
-      "integrity": "sha512-97DXOFbQJhk71ne5/Mt6cOu6yxsSfM0QGQyl0L25Gca4yGWEGJaig7l7gbCX623VqTBNGLRLaVUCnNkcedlRSQ==",
+      "integrity": "sha512-97DXOFbQJhk71ne5/Mt6cOu6yxsSfM0QGQyl0L25Gca4yGWEGJaig7l7gbCX623VqTBNGLRLaVUCnNkcedlRSQ=="
-      "dev": true
     },
     "node_modules/pretty-hrtime": {
       "version": "1.0.3",
@@ -1298,15 +1289,14 @@
       "dev": true
     },
     "autoprefixer": {
-      "version": "10.2.5",
+      "version": "10.2.6",
-      "resolved": "https://registry.npmjs.org/autoprefixer/-/autoprefixer-10.2.5.tgz",
+      "resolved": "https://registry.npmjs.org/autoprefixer/-/autoprefixer-10.2.6.tgz",
-      "integrity": "sha512-7H4AJZXvSsn62SqZyJCP+1AWwOuoYpUfK6ot9vm0e87XD6mT8lDywc9D9OTJPMULyGcvmIxzTAMeG2Cc+YX+fA==",
+      "integrity": "sha512-8lChSmdU6dCNMCQopIf4Pe5kipkAGj/fvTMslCsih0uHpOrXOPUEVOmYMMqmw3cekQkSD7EhIeuYl5y0BLdKqg==",
-      "dev": true,
       "requires": {
-        "browserslist": "^4.16.3",
+        "browserslist": "^4.16.6",
-        "caniuse-lite": "^1.0.30001196",
+        "caniuse-lite": "^1.0.30001230",
         "colorette": "^1.2.2",
-        "fraction.js": "^4.0.13",
+        "fraction.js": "^4.1.1",
         "normalize-range": "^0.1.2",
         "postcss-value-parser": "^4.1.0"
       }
@@ -1330,7 +1320,6 @@
       "version": "4.16.6",
       "resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.16.6.tgz",
       "integrity": "sha512-Wspk/PqO+4W9qp5iUTJsa1B/QrYn1keNCcEP5OvP7WBwT4KaDly0uONYmC6Xa3Z5IqnUgS0KcgLYu1l74x0ZXQ==",
-      "dev": true,
       "requires": {
         "caniuse-lite": "^1.0.30001219",
         "colorette": "^1.2.2",
@@ -1346,10 +1335,9 @@
       "dev": true
     },
     "caniuse-lite": {
-      "version": "1.0.30001228",
+      "version": "1.0.30001230",
-      "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001228.tgz",
+      "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001230.tgz",
-      "integrity": "sha512-QQmLOGJ3DEgokHbMSA8cj2a+geXqmnpyOFT0lhQV6P3/YOJvGDEwoedcwxEQ30gJIwIIunHIicunJ2rzK5gB2A==",
+      "integrity": "sha512-5yBd5nWCBS+jWKTcHOzXwo5xzcj4ePE/yjtkZyUV1BTUmrBaA9MRGC+e7mxnqXSA90CmCA8L3eKLaSUkt099IQ=="
-      "dev": true
     },
     "chalk": {
       "version": "2.4.2",
@@ -1438,10 +1426,9 @@
       }
     },
     "electron-to-chromium": {
-      "version": "1.3.736",
+      "version": "1.3.739",
-      "resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.3.736.tgz",
+      "resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.3.739.tgz",
-      "integrity": "sha512-DY8dA7gR51MSo66DqitEQoUMQ0Z+A2DSXFi7tK304bdTVqczCAfUuyQw6Wdg8hIoo5zIxkU1L24RQtUce1Ioig==",
+      "integrity": "sha512-+LPJVRsN7hGZ9EIUUiWCpO7l4E3qBYHNadazlucBfsXBbccDFNKUBAgzE68FnkWGJPwD/AfKhSzL+G+Iqb8A4A=="
-      "dev": true
     },
     "emoji-regex": {
       "version": "8.0.0",
@@ -1461,8 +1448,7 @@
     "escalade": {
       "version": "3.1.1",
       "resolved": "https://registry.npmjs.org/escalade/-/escalade-3.1.1.tgz",
-      "integrity": "sha512-k0er2gUkLf8O0zKJiAhmkTnJlTvINGv7ygDNPbeIsX/TJjGJZHuh9B2UxbsaEkmlEo9MfhrSzmhIlhRlI2GXnw==",
+      "integrity": "sha512-k0er2gUkLf8O0zKJiAhmkTnJlTvINGv7ygDNPbeIsX/TJjGJZHuh9B2UxbsaEkmlEo9MfhrSzmhIlhRlI2GXnw=="
-      "dev": true
     },
     "escape-string-regexp": {
       "version": "1.0.5",
@@ -1505,8 +1491,7 @@
     "fraction.js": {
       "version": "4.1.1",
       "resolved": "https://registry.npmjs.org/fraction.js/-/fraction.js-4.1.1.tgz",
-      "integrity": "sha512-MHOhvvxHTfRFpF1geTK9czMIZ6xclsEor2wkIGYYq+PxcQqT7vStJqjhe6S1TenZrMZzo+wlqOufBDVepUEgPg==",
+      "integrity": "sha512-MHOhvvxHTfRFpF1geTK9czMIZ6xclsEor2wkIGYYq+PxcQqT7vStJqjhe6S1TenZrMZzo+wlqOufBDVepUEgPg=="
-      "dev": true
     },
     "fs-extra": {
       "version": "9.0.1",
@@ -1740,8 +1725,7 @@
     "node-releases": {
       "version": "1.1.72",
       "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-1.1.72.tgz",
-      "integrity": "sha512-LLUo+PpH3dU6XizX3iVoubUNheF/owjXCZZ5yACDxNnPtgFuludV1ZL3ayK1kVep42Rmm0+R9/Y60NQbZ2bifw==",
+      "integrity": "sha512-LLUo+PpH3dU6XizX3iVoubUNheF/owjXCZZ5yACDxNnPtgFuludV1ZL3ayK1kVep42Rmm0+R9/Y60NQbZ2bifw=="
-      "dev": true
     },
     "normalize-path": {
       "version": "3.0.0",
@@ -1752,8 +1736,7 @@
     "normalize-range": {
       "version": "0.1.2",
       "resolved": "https://registry.npmjs.org/normalize-range/-/normalize-range-0.1.2.tgz",
-      "integrity": "sha1-LRDAa9/TEuqXd2laTShDlFa3WUI=",
+      "integrity": "sha1-LRDAa9/TEuqXd2laTShDlFa3WUI="
-      "dev": true
     },
     "parent-module": {
       "version": "1.0.1",
@@ -1903,8 +1886,7 @@
     "postcss-value-parser": {
       "version": "4.1.0",
       "resolved": "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.1.0.tgz",
-      "integrity": "sha512-97DXOFbQJhk71ne5/Mt6cOu6yxsSfM0QGQyl0L25Gca4yGWEGJaig7l7gbCX623VqTBNGLRLaVUCnNkcedlRSQ==",
+      "integrity": "sha512-97DXOFbQJhk71ne5/Mt6cOu6yxsSfM0QGQyl0L25Gca4yGWEGJaig7l7gbCX623VqTBNGLRLaVUCnNkcedlRSQ=="
-      "dev": true
     },
     "pretty-hrtime": {
       "version": "1.0.3",

daprdocs/static/code/workflow.json

@@ -0,0 +1,82 @@
+{
+    "definition": {
+      "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
+      "actions": {
+        "Function": {
+          "type": "Http",
+          "inputs": {
+            "method": "GET",
+            "uri": "https://daprfunc.azurewebsites.net/api/HttpTrigger1"
+          },
+          "runAfter": {}
+        },
+        "SaveState": {
+          "type": "Http",
+          "inputs": {
+            "method": "POST",
+            "uri": "http://localhost:3500/v1.0/state/statestore",
+            "body": [
+              {
+                "key": "mystate",
+                "value": "@body('Function')"
+              }
+            ],
+            "headers": {
+              "Content-Type": "application/json"
+            }
+          },
+          "runAfter": {
+            "Function": [
+              "Succeeded"
+            ]
+          }
+        },
+        "SendToServiceBus": {
+          "type": "Http",
+          "inputs": {
+            "method": "POST",
+            "uri": "http://localhost:3500/v1.0/bindings/servicebus",
+            "body": {
+              "data": {
+                "message": "@body('Function')"
+              }
+            },
+            "headers": {
+              "Content-Type": "application/json"
+            }
+          },
+          "runAfter": {
+            "SaveState": [
+              "Succeeded"
+            ]
+          }
+        },
+        "Response": {
+          "inputs": {
+            "body": {
+              "value": "@body('Function')"
+            },
+            "statusCode": 200
+          },
+          "runAfter": {
+            "SendToServiceBus": [
+              "Succeeded"
+            ]
+          },
+          "type": "Response"
+        }
+      },
+      "contentVersion": "1.0.0.0",
+      "outputs": {},
+      "parameters": {},
+      "triggers": {
+        "manual": {
+          "inputs": {
+            "schema": {}
+          },
+          "kind": "Http",
+          "type": "Request"
+        }
+      }
+    }
+  }

translations/docs-zh

@@ -1 +1 @@
-Subproject commit e86abb5f4cecb77fb9e08ca9dd02832e312b04a8
+Subproject commit a567aaeaafa09450e37960dc218e6875cffd7815