Enabling any resource detector disables others

[cleverchuk]

Describe the bug

Enabling a resource provider using otel.java.enabled.resource.providers to configure providers disables all resource providers not explicitly specified in the list.

Steps to reproduce
Set -Dotel.java.enabled.resource.providers=io.opentelemetry.contrib.aws.resource.EksResourceProvider

What did you expect to see?

Expect to see my service with the configured service name

What did you see instead?

A service with service.name set to unknown_service:java. This is because EnvironmentResourceProvider is filtered out and any other provider not listed is filtered as well.

What version and what artifacts are you using?
Artifacts: opentelemetry-java
Version: 1.56.0

Environment
Compiler: OpenJDK Corretto-21.0.8.9.1
OS: Mac 24.6.0
Runtime: Corretto-21.0.8.9.1

Additional context
Add any other context about the problem here.

_{Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[jkwatson]

I personally think I'd be more surprised if when I explicitly set some number of "enabled" resource providers, that I somehow got some other ones enabled that I hadn't asked for.

[cleverchuk]

@jkwatson Even more jarring when -Dotel.service.name=my-app turns into unknown_service:java because I set a resource detector.

[zeitlinger]

I'd much rather like to see feedback on the new declarative config instead of doing changes (that potentially break users) in the old config approach.

[cleverchuk]

It's already breaking as it is.

[zeitlinger]

It's already breaking as it is.

well, it works as designed - but I agree that it's confusing that EnvironmentProvider is not present - and I can't think of a case, where you'd really want to remove it.

[cleverchuk]

well, it works as designed - but I agree that it's confusing that EnvironmentProvider is not present - and I can't think of a case, where you'd really want to remove it.

make sense. so the design is flawed. a better design would have been to ask the resource provider whether it should be applied or not since it has all the context about its own operation. this way none of those extra confusing configuration would be needed.