Pablo Baeyens

> not opposed to this at all, provided the feature request gains enough popularity This is the issue with the most ':+1:' on this repository, so I think it's definitely...

Thanks for having a look, I will try to loop back with the person who reported this on our end (we use psutil on the [Datadog Agent](https://github.com/DataDog/datadog-agent)) and get the...

Hey there @giampaolo, so I haven't been able to get back to the person who originally reported this to us, but I did take a look at your suggestions and...

@giampaolo Would it be possible for you to have a look at this? Also, I wonder if I can have a timeline on when this or my previous PR #1961...

@giampaolo friendly ping, could you have a look?

Note: this should not, in principle, apply to URIs from configuration sources, otherwise we can't support things like the `yaml` provider.

Since right now we only have the `env` provider, we can explore the environment variables case. Here is some info [for Windows](https://stackoverflow.com/a/20635858) (many special characters allowed) and [for Linux](https://stackoverflow.com/a/20635858) (anything...

> The use-cases: `${ENV_${RECURSIVE}}` and `${ENV?default=something}` seem very different to me. My point is that if there is a reasonable chance that we will want to implement this, we should...

S3 provider is here, I think: open-telemetry/opentelemetry-collector-contrib/pull/13113

Should we create an checklist for each kind of component (receiver, processor, exporter, extension...)? So that this can potentially be taken on by several people