Travis Illig

Just hit this myself. I had previously written a script that basically did: - `kubectl api-resources -o name --namespaced=true` (or `--namespaced=false`, depending on what I'm looking for) - Removes anything...

I've been working on bridging this in my local solution and one way this could be addressed is with `IConfigureOptions`. First, the actual configuration (from `IConfiguration`) could be in an...

It appears that `IDeferredMeterProvider` may be able to pretty easily be updated to have a `Services` property - `MeterProviderBuilderHosting` already has a `Services` property, this would just let folks hook...

Unfortunately, it doesn't seem that does what I'm hoping. It does look like it nicely can attach things to the hosting environment, but it doesn't connect anything to `IConfiguration`. It...

I do see the calls to `services.Configure(config)` and that's not quite the same. It implies that the configuration is in the same object format as the thing being configured, like:...

@codeaphex That part where you're manually reading info and passing it to the Jaeger exporter? There is _already code_ to read that directly from the environment. Since config can include...

@CodeBlanch > Essentially the issue is the OTel spec environment variable keys are not friendly to work well with .NET IConfiguration. > > Am I understanding this correctly? Well, sort...

@CodeBlanch I could, but that breaks this: > The real key is I don't want the .NET specific stuff leaking out to the environment variables. Being language agnostic and using...

I'm more worried about confusion and precedent. "Why is it configured twice? I'm a Java person, let me PR this unnecessary duplicate out of there." "These two values can diverge....

Are there technical blockers? No, I have extension methods and configurators that already basically do what your workaround/experimentation is doing: ```c# /// /// Environment variable keys defined by the OpenTelemetry...