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

Merge branch 'v1.13' into update-app-insights-otel-collector-version

This commit is contained in:
Hannah Hunter 2024-05-30 17:02:58 -04:00 committed by GitHub
parent 1ad4765b48 4c7d58e400
commit c25b926535
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
8 changed files with 38 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
daprdocs/content/en/contributing/presentations.md
View File

@ -13,7 +13,7 @@ We welcome community members giving presentations on Dapr and spreading the word
{{% alert color="primary" %}}
If you're using the PowerPoint template with MacOS, please install the Space Grotesk font to ensure the text is rendered properly:
```sh
brew install --cask homebrew/cask-fonts/font-space-grotesk
brew install --cask font-space-grotesk
```
{{% /alert %}}

2
daprdocs/content/en/developing-applications/building-blocks/pubsub/howto-route-messages.md
View File

@ -40,7 +40,7 @@ scopes:
In the programmatic approach, the `routes` structure is returned instead of `route`. The JSON structure matches the declarative YAML:
{{< tabs Python Node "C#" Go PHP>}}
{{< tabs Python JavaScript ".NET" Go PHP>}}
{{% codetab %}}
```python

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

@ -69,17 +69,17 @@ The table below shows which applications are allowed to publish into the topics:
| | topic1 | topic2 | topic3 |
|------|--------|--------|--------|
| app1 | X | | |
| app2 | | X | X |
| app1 | ✅ | | |
| app2 | | ✅ | ✅ |
| app3 | | | |
The table below shows which applications are allowed to subscribe to the topics:
| | topic1 | topic2 | topic3 |
|------|--------|--------|--------|
| app1 | X | X | X |
| app1 | ✅ | ✅ | ✅ |
| app2 | | | |
| app3 | X | | |
| app3 | ✅ | | |
> Note: If an application is not listed (e.g. app1 in subscriptionScopes) it is allowed to subscribe to all topics. Because `allowedTopics` is not used and app1 does not have any subscription scopes, it can also use additional topics not listed above.
@ -143,17 +143,17 @@ The table below shows which application is allowed to publish into the topics:
| | A | B | C |
|------|---|---|---|
| app1 | X | | |
| app2 | X | X | |
| app3 | X | X | |
| app1 | ✅ | | |
| app2 | ✅ | ✅ | |
| app3 | ✅ | ✅ | |
The table below shows which application is allowed to subscribe to the topics:
| | A | B | C |
|------|---|---|---|
| app1 | | | |
| app2 | X | | |
| app3 | X | X | |
| app2 | ✅ | | |
| app3 | ✅ | ✅ | |
## Example 4: Mark topics as protected
@ -187,17 +187,17 @@ The table below shows which application is allowed to publish into the topics:
| | A | B | C |
|------|---|---|---|
| app1 | X | X | |
| app2 | | X | |
| app3 | | | X |
| app1 | ✅ | ✅ | |
| app2 | | ✅ | |
| app3 | | | ✅ |
The table below shows which application is allowed to subscribe to the topics:
| | A | B | C |
|------|---|---|---|
| app1 | X | X | |
| app2 | | X | |
| app3 | | | X |
| app1 | ✅ | ✅ | |
| app2 | | ✅ | |
| app3 | | | ✅ |
## Demo

12
daprdocs/content/en/operations/components/setup-pubsub/pubsub-namespaces.md
View File

@ -23,12 +23,12 @@ The table below shows which resources are deployed to which namespaces:
| Resource | namespace-a | namespace-b |
|------------------------ |-------------|-------------|
| Redis master | X | |
| Redis replicas | X | |
| Dapr's PubSub component | X | X |
| Node subscriber | X | |
| Python subscriber | X | |
| React UI publisher | | X |
| Redis master | ✅ | ❌ |
| Redis replicas | ✅ | ❌ |
| Dapr's PubSub component | ✅ | ✅ |
| Node subscriber | ✅ | ❌ |
| Python subscriber | ✅ | ❌ |
| React UI publisher | ❌ | ✅ |
{{% alert title="Note" color="primary" %}}
All pub/sub components support limiting pub/sub topics to specific applications using [namespace or component scopes]({{< ref pubsub-scopes.md >}}).

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

@ -45,6 +45,7 @@ The table below shows the versions of Dapr releases that have been tested togeth
| Release date | Runtime | CLI | SDKs | Dashboard | Status | Release notes |
|--------------------|:--------:|:--------|---------|---------|---------|------------|
| May 29th 2024 | 1.13.4</br> | 1.13.0 | Java 1.11.0 </br>Go 1.10.0 </br>PHP 1.2.0 </br>Python 1.13.0 </br>.NET 1.13.0 </br>JS 3.3.0 | 0.14.0 | Supported (current) | [v1.13.4 release notes](https://github.com/dapr/dapr/releases/tag/v1.13.4) |
| May 21st 2024 | 1.13.3</br> | 1.13.0 | Java 1.11.0 </br>Go 1.10.0 </br>PHP 1.2.0 </br>Python 1.13.0 </br>.NET 1.13.0 </br>JS 3.3.0 | 0.14.0 | Supported (current) | [v1.13.3 release notes](https://github.com/dapr/dapr/releases/tag/v1.13.3) |
| April 3rd 2024 | 1.13.2</br> | 1.13.0 | Java 1.11.0 </br>Go 1.10.0 </br>PHP 1.2.0 </br>Python 1.13.0 </br>.NET 1.13.0 </br>JS 3.3.0 | 0.14.0 | Supported (current) | [v1.13.2 release notes](https://github.com/dapr/dapr/releases/tag/v1.13.2) |
| March 26th 2024 | 1.13.1</br> | 1.13.0 | Java 1.11.0 </br>Go 1.10.0 </br>PHP 1.2.0 </br>Python 1.13.0 </br>.NET 1.13.0 </br>JS 3.3.0 | 0.14.0 | Supported (current) | [v1.13.1 release notes](https://github.com/dapr/dapr/releases/tag/v1.13.1) |
@ -138,6 +139,7 @@ General guidance on upgrading can be found for [self hosted mode]({{< ref self-h
| 1.12.0 | N/A | 1.12.4 |
| 1.13.0 | N/A | 1.13.2 |
| 1.13.0 | N/A | 1.13.3 |
| 1.13.0 | N/A | 1.13.4 |
## Upgrade on Hosting platforms

12
daprdocs/content/en/reference/api/pubsub_api.md
View File

@ -177,7 +177,15 @@ Example:
{
"pubsubname": "pubsub",
"topic": "newOrder",
"route": "/orders",
"routes": {
"rules": [
{
"match": "event.type == order",
"path": "/orders"
}
]
"default" : "/otherorders"
},
"metadata": {
"rawPayload": "true"
}
@ -197,7 +205,7 @@ Parameter | Description
### 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.
In order to deliver topic events, a `POST` call will be made to user code with the route specified in the subscription response. Under `routes`, you can provide [rules that match a certain condition to a specific path when a message topic is received.]({{< ref "howto-route-messages.md" >}}) You can also provide a default route for any rules that do not have a specific match.
The following example illustrates this point, considering a subscription for topic `newOrder` with route `orders` on port 3000: `POST http://localhost:3000/orders`

4
daprdocs/content/en/reference/cli/dapr-init.md
View File

@ -71,10 +71,10 @@ dapr init -s
**Specify a runtime version**
You can also specify a specific runtime version. Be default, the latest version is used.
You can also specify a specific runtime version. By default, the latest version is used.
```bash
dapr init --runtime-version 1.13.3
dapr init --runtime-version 1.13.4
```
**Install with image variant**

2
daprdocs/layouts/shortcodes/dapr-latest-version.html
View File

@ -1 +1 @@
{{- if .Get "short" }}1.13{{ else if .Get "long" }}1.13.3{{ else if .Get "cli" }}1.13.3{{ else }}1.13.3{{ end -}}
{{- if .Get "short" }}1.13{{ else if .Get "long" }}1.13.4{{ else if .Get "cli" }}1.13.4{{ else }}1.13.4{{ end -}}