[ICPRO-41] Add SDK_CONFIGURATION RC parametric coverage

[mtoffl01]

Motivation

Tracers are migrating away from reporting one APM_TRACING_* Remote Config capability bit per setting, toward a single SDK_CONFIGURATION bit that covers a generic, env-var-keyed sdk_config payload (a sibling of the legacy lib_config payload). As each tracer makes that switch, we want confidence that settings already covered by the legacy per-field bits keep behaving the same way once delivered via sdk_config instead — i.e. that the migration doesn't quietly change behavior.

RFC: https://docs.google.com/document/d/13aKzR8U97-yzaJZDs8rnNVGn4C1NCmfPhAoDkBtH9NM/edit?tab=t.0#heading=h.f9tdtrzge1bf

This PR adds parametric coverage for that: a tracer that declares SDK_CONFIGURATION should apply sdk_config the same way it used to apply the equivalent lib_config setting.

What changed?

TestDynamicConfigSdkConfiguration in tests/parametric/test_dynamic_configuration.py is a new test class covering the sdk_config delivery path. test_capability_sdk_configuration and test_sdk_config_tracing_enabled_matches_lib_config confirm DD_TRACE_ENABLED delivered via sdk_config disables tracing the same way the legacy lib_config/env-var path does. test_sdk_config_profiling_enabled covers DD_PROFILING_ENABLED, which has no lib_config equivalent to compare against (it only exists in sdk_config), so it just checks the tracer reports the setting as applied.

test_sdk_config_field_is_applied is a single parametrized test that loops over every lib_config setting with a corresponding APM_TRACING_* capability bit, and, for each one this tracer version actually declares (checked live against capabilities.yml), delivers it via sdk_config and asserts it was applied — using non-default test values so a tracer that silently no-ops on sdk_config can't pass by accident. Not every one of those settings has a test_telemetry.py name-mapping entry yet; where one's missing, the assertion fails with a message pointing at the gap, so whichever tracer next needs that setting covered will discover it there rather than the coverage being silently skipped.

Since no tracer implements SDK_CONFIGURATION today, the whole class is gated as missing_feature in every language's manifest.

Test plan

• ./format.sh --check (mypy/ruff passed locally; yamlfmt step failed locally due to an unrelated macOS tooling issue, confirmed via direct yaml.safe_load validation of edited manifests)
• CI parametric test run

🤖 Generated with Claude Code

[github-actions]

CODEOWNERS have been resolved as:

manifests/cpp.yml                                                       @DataDog/system-tests-reviewers
manifests/dotnet.yml                                                    @DataDog/system-tests-reviewers
manifests/golang.yml                                                    @DataDog/system-tests-reviewers
manifests/java.yml                                                      @DataDog/system-tests-reviewers
manifests/nodejs.yml                                                    @DataDog/system-tests-reviewers
manifests/php.yml                                                       @DataDog/system-tests-reviewers
manifests/python.yml                                                    @DataDog/system-tests-reviewers
manifests/ruby.yml                                                      @DataDog/system-tests-reviewers
manifests/rust.yml                                                      @DataDog/system-tests-reviewers
tests/parametric/test_dynamic_configuration.py                          @DataDog/system-tests-core @DataDog/apm-sdk-capabilities
tests/parametric/test_telemetry.py                                      @DataDog/system-tests-core @DataDog/apm-sdk-capabilities
tests/parametric/utils.py                                               @DataDog/system-tests-core @DataDog/apm-sdk-capabilities

[datadog-datadog-prod-us1]

 

⚠️ Warnings

❌ Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 2 Pipeline jobs failed

Testing the test | System Tests (nodejs, prod) / End-to-end #1 / express4-typescript 1

View more details · View in GitHub Actions

Error: read ECONNRESET during request; Container weblog is not running (exited) as per logs.

Testing the test | all-jobs-are-green

View more details · View in GitHub Actions

Job did not run: blocked by a failed job in an earlier pipeline stage.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 70b88c4 | Docs | View more details | Give us feedback!}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f91c9e4f6f

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".