Merging multiple configuration sources #1488
-
Is it possible to combine multiple configuration sources? Specifically I'm interested in a case where some parts of the configuration are defined in config/code and the rest is produced out of the k8s controller. I'm imaging an instance where you'd want to include a single set of transforms across all routes, but still use the k8s controller to read from ingresses. For example, you might have a series of headers that you want added to all routes--something you can't currently set directly on an Ingress but would want to avoid repeating even if you could. I'm also thinking of defining "Exact" Ingress paths with placeholders in them, ie. Or am I thinking about this all wrong and overlooking the correct way of doing this? Do I simply just chain |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
If you only want to modify existing routes, then yes AddTransforms is a good way to do that. There are also config filters if you want to tweak the raw model before it's processed. |
Beta Was this translation helpful? Give feedback.
If you only want to modify existing routes, then yes AddTransforms is a good way to do that.
reverse-proxy/samples/ReverseProxy.Transforms.Sample/Startup.cs
Line 39 in 23d235f
There are also config filters if you want to tweak the raw model before it's processed.
reverse-proxy/samples/ReverseProxy.ConfigFilter.Sample/CustomConfigFilter.cs
Line 55 in 23d235f