Component

Config

Problem Statement

When otelconf builds an SDK from declarative configuration, downstream users have no supported way to read back the final resource that the SDK is actually using.

This creates a problem for projects that need to surface resource attributes outside the SDK providers (for example, converting resource data into another internal representation).

Proposed Solution

Expose stable public method to access the effective SDK resource produced by otelconf after configuration is applied.

Alternatives

No response

Prior Art

No response

Additional Context

No response