Skip to content

fix(config): do not set propagators by default#6234

Closed
yoursanonymous wants to merge 3 commits intoopen-telemetry:mainfrom
yoursanonymous:config-propogators
Closed

fix(config): do not set propagators by default#6234
yoursanonymous wants to merge 3 commits intoopen-telemetry:mainfrom
yoursanonymous:config-propogators

Conversation

@yoursanonymous
Copy link
Copy Markdown

Which problem is this PR solving?

This PR fixes an issue where initializeDefaultConfiguration() implicitly configured text map propagators by default.

Fixes #6150

Short description of the changes

Removed default propagator configuration from initializeDefaultConfiguration
Added a unit test to ensure propagators are not set by default
Added a unit test to verify propagators are configured when OTEL_PROPAGATORS is explicitly defined

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Added unit tests covering default and environment-based propagator behavior
Tests executed locally using: npx mocha test/utils.test.ts

Checklist:

  • Followed the style guidelines of this project
  • Unit tests have been added
  • Documentation has been updated

@yoursanonymous yoursanonymous requested a review from a team as a code owner December 17, 2025 23:01
});
});

it('should set propagators from OTEL_PROPAGATORS when defined', () => {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this file focus on testing functions from the utils file, which is not the case for this test, so you can remove from here and update the ConfigFactory.test.js file accordingly

const rawValue = keyPairPart.substring(separatorIndex + 1).trim();

if (!rawKey || !rawValue) return;
if (!rawKey) return;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you explain the rationale behind this change and the one below? they don't seem related to your PR topic

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can see these changes are from your other PR, so please remove them from here

@maryliag
Copy link
Copy Markdown
Contributor

Hey @yoursanonymous , friendly ping to check fi you still plan on working on this

@maryliag
Copy link
Copy Markdown
Contributor

Closing in favor of #6399

@maryliag maryliag closed this Feb 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Config should not have default propagators

2 participants