Merge branch 'v0.11' into periodic-rc2

daprdocs/content/en/contributing/contributing-docs.md

@@ -39,7 +39,7 @@ These conventions should be followed throughout all Dapr documentation to ensure
 ## Contributing a new docs page
 - Make sure the documentation you are writing is in the correct place in the hierarchy. 
 - Avoid creating new sections where possible, there is a good chance a proper place in the docs hierarchy already exists.
-- Make sure to include a complete [Hugo front-matter](front-matter).
+- Make sure to include a complete [Hugo front-matter](#front-matter).
 
 ### Contributing a new concept doc
 - Ensure the reader can understand why they should care about this feature. What problems does it help them solve?

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

@@ -53,7 +53,7 @@ Dapr allows two methods by which you can subscribe to topics: **declarative**, w
 
 ### Message Delivery
 
-In principle, Dapr considers message successfully delivered when the subscriber responds with a non-error response after processing the message. For more granular control, Dapr's publish/subscribe API also provides explicit statuses, defined in the response payload, which the subscriber can use to indicate the specific handling instructions to Dapr (e.g. `RETRY` or `DROP`). For more information message routing see [Dapr publish/subscribe API documentation] ({{< ref "pubsub_api.md#provide-routes-for-dapr-to-deliver-topic-events" >}})
+In principle, Dapr considers message successfully delivered when the subscriber responds with a non-error response after processing the message. For more granular control, Dapr's publish/subscribe API also provides explicit statuses, defined in the response payload, which the subscriber can use to indicate the specific handling instructions to Dapr (e.g. `RETRY` or `DROP`). For more information message routing see [Dapr publish/subscribe API documentation]({{< ref "pubsub_api.md#provide-routes-for-dapr-to-deliver-topic-events" >}})
 
 ### At-Least-Once guarantee
 

daprdocs/content/en/developing-applications/building-blocks/state-management/query-state-store/query-sqlserver-store.md

@@ -19,17 +19,17 @@ The easiest way to connect to your SQL Server instance is to use the [Azure Data
 To get all state keys associated with application "myapp", use the query:
 
 ```sql
-SELECT * FROM states WHERE [Key] LIKE 'myapp-%'
+SELECT * FROM states WHERE [Key] LIKE 'myapp||%'
 ```
 
-The above query returns all rows with id containing "myapp-", which is the prefix of the state keys.
+The above query returns all rows with id containing "myapp||", which is the prefix of the state keys.
 
 ## 3. Get specific state data
 
 To get the state data by a key "balance" for the application "myapp", use the query:
 
 ```sql
-SELECT * FROM states WHERE [Key] = 'myapp-balance'
+SELECT * FROM states WHERE [Key] = 'myapp||balance'
 ```
 
 Then, read the **Data** field of the returned row.
@@ -37,7 +37,7 @@ Then, read the **Data** field of the returned row.
 To get the state version/ETag, use the command:
 
 ```sql
-SELECT [RowVersion] FROM states WHERE [Key] = 'myapp-balance'
+SELECT [RowVersion] FROM states WHERE [Key] = 'myapp||balance'
 ```
 
 ## 4. Get filtered state data
@@ -53,13 +53,13 @@ SELECT * FROM states WHERE JSON_VALUE([Data], '$.color') = 'blue'
 To get all the state keys associated with an actor with the instance ID "leroy" of actor type "cat" belonging to the application with ID "mypets", use the command:
 
 ```sql
-SELECT * FROM states WHERE [Key] LIKE 'mypets-cat-leroy-%'
+SELECT * FROM states WHERE [Key] LIKE 'mypets||cat||leroy||%'
 ```
 
 And to get a specific actor state such as "food", use the command:
 
 ```sql
-SELECT * FROM states WHERE [Key] = 'mypets-cat-leroy-food'
+SELECT * FROM states WHERE [Key] = 'mypets||cat||leroy||food'
 ```
 
 > **WARNING:** You should not manually update or delete states in the store. All writes and delete operations should be done via the Dapr runtime.

daprdocs/content/en/developing-applications/ides/codespaces.md

@@ -0,0 +1,32 @@
+---
+type: docs
+title: "Developing with GitHub Codespaces"
+linkTitle: "GitHub Codespaces"
+weight: 3000
+description: "How to get up and running with Dapr in a GitHub Codespace"
+---
+
+[GitHub Codespaces](https://github.com/features/codespaces) are the easiest way to get up and running in a Dapr environment. In as little as a single click you have the environment, packages, code, samples, and documentation all ready to go in your browser.
+
+{{% alert title="Private Beta" color="warning" %}}
+GitHub Codespaces is currently in a private beta. Sign up [here](https://github.com/features/codespaces/signup).
+{{% /alert %}}
+
+## Features
+
+- **Click and Run**: Get a dedicated and sandboxed environment with all of the required frameworks and packages ready to go.
+- **Usage-based Billing**: Only pay for the time you spend developing in the Codespace. Environments are spun down automatically when not in use.
+- **Portable**: Run in your browser or in Visual Studio Code
+
+## Open a Dapr repo in a Codespace
+
+To open a Dapr repository in a Codespace simply select "Code" from the repo homepage and "Open with Codespaces":
+
+<img src="/images/codespaces-create.png" alt="Screenshot of creating a Dapr Codespace" width="300">
+
+### Supported repos
+
+- [Python SDK](https://github.com/dapr/python-sdk)
+
+## Related links
+- [GitHub documentation](https://docs.github.com/en/github/developing-online-with-codespaces/about-codespaces)

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

@@ -662,6 +662,6 @@ The state namespace created by Dapr for actors is composed of the following item
 - Key - A key for the specific state value. An actor ID can hold multiple state keys.
 
 The following example shows how to construct a key for the state of an actor instance under the `myapp` App ID namespace:
-`myapp-cat-hobbit-food`
+`myapp||cat||hobbit||food`
 
 In the example above, we are getting the value for the state key `food`, for the actor ID `hobbit` with an actor type of `cat`, under the App ID namespace of `myapp`.

daprdocs/static/docs/open-telemetry-collector/open-telemetry-collector.yaml

@@ -10,9 +10,6 @@ data:
     receivers:
       zipkin:
         endpoint: 0.0.0.0:9411
-    processors:
-      queued_retry:
-      batch:
     extensions:
       health_check:
       pprof:
@@ -37,7 +34,6 @@ data:
         traces:
           receivers: [zipkin]
           exporters: [azuremonitor,logging]
-          processors: [batch, queued_retry]
 ---
 apiVersion: v1
 kind: Service