mirror of https://github.com/dapr/docs.git
Merge branch 'v0.11' into periodic-rc2
This commit is contained in:
commit
4579d1e16c
|
@ -39,7 +39,7 @@ These conventions should be followed throughout all Dapr documentation to ensure
|
||||||
## Contributing a new docs page
|
## Contributing a new docs page
|
||||||
- Make sure the documentation you are writing is in the correct place in the hierarchy.
|
- 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.
|
- 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
|
### Contributing a new concept doc
|
||||||
- Ensure the reader can understand why they should care about this feature. What problems does it help them solve?
|
- Ensure the reader can understand why they should care about this feature. What problems does it help them solve?
|
||||||
|
|
|
@ -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:
|
To get all state keys associated with application "myapp", use the query:
|
||||||
|
|
||||||
```sql
|
```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
|
## 3. Get specific state data
|
||||||
|
|
||||||
To get the state data by a key "balance" for the application "myapp", use the query:
|
To get the state data by a key "balance" for the application "myapp", use the query:
|
||||||
|
|
||||||
```sql
|
```sql
|
||||||
SELECT * FROM states WHERE [Key] = 'myapp-balance'
|
SELECT * FROM states WHERE [Key] = 'myapp||balance'
|
||||||
```
|
```
|
||||||
|
|
||||||
Then, read the **Data** field of the returned row.
|
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:
|
To get the state version/ETag, use the command:
|
||||||
|
|
||||||
```sql
|
```sql
|
||||||
SELECT [RowVersion] FROM states WHERE [Key] = 'myapp-balance'
|
SELECT [RowVersion] FROM states WHERE [Key] = 'myapp||balance'
|
||||||
```
|
```
|
||||||
|
|
||||||
## 4. Get filtered state data
|
## 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:
|
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
|
```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:
|
And to get a specific actor state such as "food", use the command:
|
||||||
|
|
||||||
```sql
|
```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.
|
> **WARNING:** You should not manually update or delete states in the store. All writes and delete operations should be done via the Dapr runtime.
|
||||||
|
|
|
@ -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)
|
|
@ -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.
|
- 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:
|
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`.
|
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`.
|
||||||
|
|
|
@ -10,9 +10,6 @@ data:
|
||||||
receivers:
|
receivers:
|
||||||
zipkin:
|
zipkin:
|
||||||
endpoint: 0.0.0.0:9411
|
endpoint: 0.0.0.0:9411
|
||||||
processors:
|
|
||||||
queued_retry:
|
|
||||||
batch:
|
|
||||||
extensions:
|
extensions:
|
||||||
health_check:
|
health_check:
|
||||||
pprof:
|
pprof:
|
||||||
|
@ -37,7 +34,6 @@ data:
|
||||||
traces:
|
traces:
|
||||||
receivers: [zipkin]
|
receivers: [zipkin]
|
||||||
exporters: [azuremonitor,logging]
|
exporters: [azuremonitor,logging]
|
||||||
processors: [batch, queued_retry]
|
|
||||||
---
|
---
|
||||||
apiVersion: v1
|
apiVersion: v1
|
||||||
kind: Service
|
kind: Service
|
||||||
|
|
Binary file not shown.
After Width: | Height: | Size: 56 KiB |
Loading…
Reference in New Issue