All default resource providers are disabled when setting `otel.resource.providers.aws.enabled=true`

[jessestricker]

Describe the bug

Enabling the AWS resource provider when running the Java agent by setting otel.resource.providers.aws.enabled=true disables all builtint resource providers, including the one which sets resource attributes from the environment variable OTEL_RESOURCE_ATTRIBUTES.

I that that if I use the setting otel.java.enabled.resource.providers that all the builtin providers are disabled except for the ones specified, and that is documented as such just fine.

However, this seems to apply to the otel.resource.providers.<name>.enabled settings as-well, enabling one of them also disables all other default providers.
IMO, this is not made sufficiently clear in the documentation, where it says that "you can enable additional resource providers".

Steps to reproduce

Run a Java application with the Java agent and set the following environment variables:

OTEL_RESOURCE_ATTRIBUTES=foo=bar
OTEL_RESOURCE_PROVIDERS_AWS_ENABLE=true

In the emitted telemetry, the resource foo can not be seen because the io.opentelemetry.sdk.autoconfigure.EnvironmentResourceProvider was disabled.

Expected behavior

I would expect to retain all the default providers when I use a setting of the form otel.resource.providers.<name>.enabled.

Alternatively, the documentation can be clarified that enabling resource providers via the otel.resource.providers.<name>.enabled setting does in fact disable all the default ones.

Actual behavior

See description above.

Javaagent or library instrumentation version

2.18.1

Environment

JDK: 21
OS: Tested on Windows 11 and Amazon Linux

Additional context

No response

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.}

[laurit]

I tried it out but wasn't able to reproduce. I ran

    public static void main(String... args) throws Exception {
        Tracer tracer = io.opentelemetry.api.GlobalOpenTelemetry.get().getTracer("test");
        tracer.spanBuilder("test").startSpan().end();
    }

with agent built from main (there shouldn't be any changes since the last release that would affect this) with OTEL_RESOURCE_ATTRIBUTES=foo=bar OTEL_RESOURCE_PROVIDERS_AWS_ENABLE=true and it worked as expected.
The code for this is in

opentelemetry-java-instrumentation/sdk-autoconfigure-support/src/main/java/io/opentelemetry/instrumentation/resources/ResourceProviderPropertiesCustomizer.java

Line 64 in 28d7b15

public Map<String, String> customize(ConfigProperties config) {

By default the aws providers are disabled and are automatically added to otel.java.disabled.resource.providers When otel.resource.providers.aws.enabled=true is set then disabling is skipped. If otel.java.enabled.resource.providers is set then aws providers are added there when they are enabled with otel.resource.providers.aws.enabled=true.

[breedx-splk]

I tried with petclinic and could also not reproduce this.

[jessestricker]

Yes, I've tried again in a minimal setup and can't reproduce it.
It was something else in our existing project which caused the environment variable not being picked up correctly.

Sorry for any inconvenience.