dotnet / dotnet/yarp

[Idea] Allow routing based on partial or complete route params

Open
#1,609 6 comments 4 reactions 0 assignees View on GitHub
Type: Idea
Dominant language
C#
Stars
9.6k
Forks
933
Avg merge
12d 18h
Merged PRs (30d)
2

Description

### What should we add or change to make your life better?

Hello,

It's currently possible to perform routing based on headers and query parameters.
How open would you be to extend `RouteMatch` to have it expose a `RouteParam` sub matcher. This one would be very similar to `RouteQueryParameter` (accepting values, a mode, ...).

Given, for instance, a route such as `/api/tenants/{tenant_id}/do/something`, it would be easy to redirect the requests based on the value of `tenant_id`.

### Why is this important to you?

In order to meet regulations, data from those tenants should be stored in selected geographical locations.

Would this feature request feel appropriate, I'd be very willing to help contribute it through a Pull Request.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.