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

Merge branch 'v1.12' into bulk_pubsub_optimization_paths

This commit is contained in:
Hannah Hunter 2023-10-11 18:17:58 -04:00 committed by GitHub
parent ec7e1f5e0a 06eb43d36e
commit be1936c84c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
daprdocs/content/en/reference/components-reference/supported-middleware/middleware-routeralias.md
View File

@ -7,12 +7,10 @@ aliases:
- /developing-applications/middleware/supported-middleware/middleware-routeralias/ - /developing-applications/middleware/supported-middleware/middleware-routeralias/
--- ---
The router alias HTTP [middleware]({{< ref middleware.md >}}) component allows you to convert arbitrary HTTP routes arriving to Dapr to valid Dapr API endpoints. The router alias HTTP [middleware]({{< ref middleware.md >}}) component allows you to convert arbitrary HTTP routes arriving into Dapr to valid Dapr API endpoints.
## Component format ## Component format
The router alias middleware metadata contains name/value pairs, where the name describes the HTTP route to expect, and the value describes the corresponding Dapr API the request should be sent to.
```yaml ```yaml
apiVersion: dapr.io/v1alpha1 apiVersion: dapr.io/v1alpha1
kind: Component kind: Component
@ -22,17 +20,24 @@ spec:
type: middleware.http.routeralias type: middleware.http.routeralias
version: v1 version: v1
metadata: metadata:
- name: "/v1.0/mall/activity/info" # String containing a JSON-encoded or YAML-encoded dictionary
value: "/v1.0/invoke/srv.default/method/mall/activity/info" # Each key in the dictionary is the incoming path, and the value is the path it's converted to
- name: "/v1.0/hello/activity/{id}/info" - name: "routes"
value: "/v1.0/invoke/srv.default/method/hello/activity/info" value: |
- name: "/v1.0/hello/activity/{id}/user" {
value: "/v1.0/invoke/srv.default/method/hello/activity/user" "/mall/activity/info": "/v1.0/invoke/srv.default/method/mall/activity/info",
"/hello/activity/{id}/info": "/v1.0/invoke/srv.default/method/hello/activity/info",
"/hello/activity/{id}/user": "/v1.0/invoke/srv.default/method/hello/activity/user"
}
``` ```
Example: In the example above, an incoming HTTP request for `/mall/activity/info?id=123` is transformed into `/v1.0/invoke/srv.default/method/mall/activity/info?id=123`.
An incoming HTTP request for `/v1.0/mall/activity/info?id=123` is transformed into `/v1.0/invoke/srv.default/method/mall/activity/info?id=123`. # Spec metadata fields
| Field | Details | Example |
|-------|---------|---------|
| `routes` | String containing a JSON-encoded or YAML-encoded dictionary. Each key in the dictionary is the incoming path, and the value is the path it's converted to. | See example above |
## Dapr configuration ## Dapr configuration