[CONFIGURATION] Split programmatic and YAML cmake targets

[pranitaurlam]

Fixes #4134

Summary

• Splits opentelemetry_configuration into two CMake targets:
  • opentelemetry_configuration: programmatic configuration only (sdk_builder.cc, configured_sdk.cc, registry.cc, configuration_parser.cc, document_node.cc, composable sampler builders). No ryml dependency. Built unconditionally as part of the SDK.
  • opentelemetry_configuration_yaml: YAML configuration components (yaml_configuration_parser.cc, ryml_document.cc, ryml_document_node.cc) with the ryml::ryml dependency. Gated by WITH_CONFIGURATION.
• Repurposes WITH_CONFIGURATION to gate only the YAML/ryml target.
• Adds a default constructor to Configuration so it can be instantiated programmatically without a Document.
• Updates cmake component names: configuration_yaml replaces configuration for the YAML component; the configuration component is now the programmatic-only piece included in the SDK.

Test plan

• Build without WITH_CONFIGURATION and verify opentelemetry_configuration links successfully without ryml
• Build with WITH_CONFIGURATION=ON and verify both targets build and tests pass
• Verify the example programmatic configuration from the issue compiles against opentelemetry_configuration alone

cc @lalitb @marcalff @lalitb @dbarker @ThomsonTan

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: pranitaurlam / name: pranitaurlam (2a5f743, 9c36d75, a7a35d4, e3d8512, eab1f2b, efe4b12)

[pranitaurlam]

Hi @lalitb @marcalff @lalitb @dbarker @ThomsonTan

I've opened PR #4138 to resolve issue #4134 — splitting the opentelemetry_configuration CMake target into two separate targets so users can use programmatic configuration without pulling in the ryml dependency.

The EasyCLA check has passed. Could one of you please approve the workflow runs so CI can execute? Any feedback on the implementation is also very welcome.

Thank you!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.82%. Comparing base (17c4723) to head (499e3ac).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4138   +/-   ##
=======================================
  Coverage   82.82%   82.82%           
=======================================
  Files         406      406           
  Lines       16913    16913           
=======================================
  Hits        14007    14007           
  Misses       2906     2906           

Files with missing lines	Coverage Δ
...de/opentelemetry/sdk/configuration/configuration.h	100.00% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[marcalff]

Thanks for the fix.

EDIT 2026-06-16: no longer needed due to renaming to opentelemetry_configuration_core, opentelemetry_configuration.

Please add an "Important note" in the CHANGELOG, to explain that user makefiles are affected, and needs to be adjusted, to use the new opentelemetry_configuration_yaml library.

Will merge after that.

[dbarker]

Thanks for the PR! Please see initial feedback and a question below.

[dbarker]

Please add a check that the ryml target has been imported.

[dbarker]

is coupling the Configuration class with the parsed document still required?

[dbarker]

@pranitaurlam Thanks for the contribution. Marc and I discussed the PR in the SIG meeting today and request the following changes to minimize impact on current users of the configuration CMake component and opentelemetry-cpp::configuration CMake target.

Instead of placing the yaml components in the configuration_yaml target we suggest:

1. Create a new CMake target opentelemetry-cpp::configuration_core to include the programmatic configuration objects. This new target should be built unconditionally with the SDK.
2. Update the configuration CMake component and opentelemetry-cpp::configuration CMake target to link to configuration_core and include only the yaml objects and ryml dependency. This component and target should still be guarded by the WITH_CONFIGURATION CMake option.

This way current users of the yaml config will continue to link to the opentelemetry-cpp::configuration target and new users of the programmatic config can link to opentelemetry-cpp::configuration_core.

[marcalff]

So, in short:

• rename opentelemetry-cpp::configuration to opentelemetry-cpp::configuration_core
• rename opentelemetry-cpp::configuration_yaml to opentelemetry-cpp::configuration

This way, applications using opentelemetry-cpp::configuration in their makefiles will be unchanged.