Tyler Helmuth
Tyler Helmuth
@mx-psi I see a couple approaches. 1. Allow `envprovider` to expand `${env:}` and `${}`. This is conceptually simple, but I think breaks some logic in `resolver.expandValue` that requires providers to...
> I think we should do it without the awareness of any of the Providers by prepending the default schema to the URI when the URI is given to the...
> If we go with (4), for now I don't think we need to make this configurable anywhere other than the Go API, but we can open the door to...
> It's not strictly required now, but it's better in that we don't need people to update their import paths for this after profiling goes to 1.0 I guess the...
What would we do if it needs to be modified instead of removed?
It is likely that this is happening bc our healthcheck extension needs improved: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/26661
I mean the current version of `extension/healthcheck` has some issues that results in readiness and liveliness not being 100% perfect. There is ongoing work to fix the issues, but it...
I haven't looked in depth yet, but my guess is that the `context.Context` that holds the request information is lost when the data is added to the persistent queue -...
@grandwizard28 do you have link to where the override is happening?
This feels like a pretty confusing topic, so I'm gonna try to define a bunch of terms for use in this comment. Currently we have the following important terms: -...