How to access Ocelot config outside of Ocelot pipeline?

[rwestonbutler]

Is there a way to access the strongly typed Ocelot configuration from outside of the Ocelot pipeline in a delegating handler or middleware, maybe have it injected via DI?

I've run into a situation where I need to grab a config value based on a part of the upstream path.

[margaale]

We have the issue #738 exactly for that, is gonna take a while though...

[rwestonbutler]

Gotcha, thank you!

[raman-m]

Hey @rwestonbutler and @margaale!
How were your holidays? 😉
Pay attention that #738 is accepted but it is still in development waiting for development.
But it describes a bit different scenario with custom properties and seems custom properties will not be strongly typed.

[raman-m]

@rwestonbutler on Jan 16, 2019:

Is there a way to access the strongly typed Ocelot configuration from outside of the Ocelot pipeline in a delegating handler or middleware, maybe have it injected via DI?

Please try to inject the following interface objects:

• IInternalConfiguration: see usage and code. It has Routes property and you have to find your route mannually.
• IOptionsMonitor<IInternalConfiguration>: see usage and code. But it requires to write valid path to extract.
• IOptions<FileConfiguration>: see usage and code. Seems it is the best option!

Hope it helps!
Let us know your testing results please!