-
Notifications
You must be signed in to change notification settings - Fork 838
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow grouping and inheriting route config #164
Comments
Do you have an example? What will be different between the routes? Is it just the path to match? In which case would having AND / OR functionality in the paths enable a single route to match a wider set of URIs? |
The example given in #134 was Host. If you have 20 routes with different paths but all with the same Host then it would be convenient to group those together so you only have to define the Host once.
You mean something like |
Another request: #122 (comment) Have a shared authorization policy for a group of routes. |
IProxyConfigFilter has proven to be a useful approach to this problem, letting people provide a basic config and to programmatically fill in bulk data.
|
Alternate proposal for the json based config: If someone defines a route/cluster named "defaults" this would not be rendered into its own route/cluster instance, it would be used to fill in default values for other routes/clusters.
|
This reminds me of CSS or Styles in XAML - it seems great to have these kinds of inheritance rules, until you have to figure out what the resulting matrix looks like. These properties define the security rules for your site, and so it needs to be clear what will actually get applied - we don't have good route diagnostics and debugging today (I thought we had a work item for that but can't find it), until we have that I think we should hold off any features here. |
Another request for adding a transform to all routes: #1928 |
The config model can get very redundant if you need to define the same property with the same value on many routes. E.g. the Host, BackendId, Metadata, auth, etc..
It may be possible to allow a config structure where routes can be grouped together and inherit some properties (backendid, Prority, metadata, auth, Host, etc.).
The text was updated successfully, but these errors were encountered: