test(ffe): enable Node.js agentless configuration

[leoromanovsky]

Motivation

DataDog/dd-trace-js#9397 adds the Node.js agentless Feature Flagging configuration source and is targeted for v6.5.0 through DataDog/dd-trace-js#9414. The shared configuration-source contract is already on main; Node.js now needs its manifest activation and updated default Remote Configuration capability expectation.

The contract also provides the cross-repository motivation for DataDog/dd-trace-js#9468: local and controlled custom agentless endpoints must be reachable, missing authentication must be observable, and unsupported source values must fail without contacting either delivery surface.

Changes

• Enable tests/parametric/test_ffe/test_configuration_sources.py for Node.js starting with v6.5.0.
• Stop expecting the FFE Remote Configuration capability in the default Node.js capability set from v6.5.0 onward.
• Keep provider startup errors inside the Node.js parametric controller /ffe/start response so negative source tests can assert startup failure and zero CDN or Remote Configuration traffic.

Decisions

• Use an explicit v6.5.0 manifest gate rather than enabling the suite for older Node.js tracer versions.
• Preserve the default capability expectation for >=5.72.0 <6.5.0; from v6.5.0, capability 46 and the FFE_FLAGS product are registered only when Feature Flags explicitly selects remote_config, which the existing configuration-source contract validates.
• Treat unsupported provider-source exceptions as a failed start response rather than allowing the parametric process to terminate before the shared assertions run.

[github-actions]

CODEOWNERS have been resolved as:

manifests/nodejs.yml                                                    @DataDog/dd-trace-js
tests/parametric/capabilities.yml                                       @DataDog/system-tests-core @DataDog/apm-sdk-capabilities
utils/build/docker/nodejs/parametric/server.js                          @DataDog/dd-trace-js @DataDog/system-tests-core

[datadog-datadog-us1-prod]

 

⚠️ Warnings

🚦 4 Pipeline jobs failed

Testing the test | System Tests (nodejs, prod) / parametric / parametric (1)     

🧪 1 Test failed

tests.parametric.test_library_tracestats.Test_Library_Tracestats.test_metrics_computed_after_span_finsh_TS009[agent_env0-library_env0, parametric-nodejs] from system_tests_suite  

AssertionError: There should be one bucket containing the stats
assert 2 == 1
 +  where 2 = len([{'Duration': 10000000000, 'Start': 1784677210000000000, 'Stats': [{'Duration': 7256836, 'ErrorSummary': store: {}}, m...y:0, offset:0, zero_count: 0.0, count: 0.0, sum: 0.0, min: inf, max: -inf, 'Errors': 0, 'GRPCStatusCode': None, ...}]}])

self = <tests.parametric.test_library_tracestats.Test_Library_Tracestats object at 0x7f09129434d0>
test_agent = <utils.docker_fixtures._test_agent.TestAgentAPI object at 0x7f08e2c0c590>
test_library = <utils.docker_fixtures._test_clients._test_client_parametric.ParametricTestClientApi object at 0x7f08e2c0d4c0>

    @enable_tracestats()
    @enable_agent_version()
...

Testing the test | System Tests (nodejs, dev) / parametric / parametric (2)     

🧪 15 Tests failed

tests.parametric.test_ffe.test_configuration_sources.Test_Feature_Flag_Configuration_Source_Cold_Failure_And_Recovery.test_bad_to_good_cold_recovery[server-error-to-valid, parametric-nodejs] from system_tests_suite  

AssertionError: failed to start FFE provider for bad_to_good
assert False
 +  where False = <bound method ParametricTestClientApi.ffe_start of <utils.docker_fixtures._test_clients._test_client_parametric.ParametricTestClientApi object at 0x7f9fb55b5340>>()
 +    where <bound method ParametricTestClientApi.ffe_start of <utils.docker_fixtures._test_clients._test_client_parametric.ParametricTestClientApi object at 0x7f9fb55b5340>> = <utils.docker_fixtures._test_clients._test_client_parametric.ParametricTestClientApi object at 0x7f9fb55b5340>.ffe_start

self = <tests.parametric.test_ffe.test_configuration_sources.Test_Feature_Flag_Configuration_Source_Cold_Failure_And_Recovery object at 0x7f9fb612bd10>
test_library = <utils.docker_fixtures._test_clients._test_client_parametric.ParametricTestClientApi object at 0x7f9fb55b5340>
mock_ffe_agentless_backend = <utils.docker_fixtures._mock_ffe_agentless_backend.MockFFEAgentlessBackendServer object at 0x7f9fb55b4350>
expected_status_codes = [500, 200]

...

tests.parametric.test_ffe.test_configuration_sources.Test_Feature_Flag_Configuration_Source_Cold_Failure_And_Recovery.test_bad_to_unchanged_cold_preserves_not_ready[server-error-to-unchanged, parametric-nodejs] from system_tests_suite  

mock FFE agentless backend status did not reach expected state: bad_to_unchanged 500 to 304 cold sequence; status={'requests_total': 0, 'in_flight': 0, 'max_in_flight': 0, 'last_path': None, 'last_if_none_match': None, 'last_auth_present': False, 'last_status_code': None, 'status_codes': []}

View all failed tests

DataDog/system-tests | noop     

View all 4 failed jobs.

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: a5dc9b8 | Docs | Datadog PR Page | Give us feedback!}