[AAS] Set DataPipelineEnabled=0 by default#7943
Merged
lucaspimentel merged 1 commit intomasterfrom Dec 10, 2025
Merged
Conversation
lucaspimentel
approved these changes
Dec 10, 2025
|
DataPipelineEnabled=0 by defaultDataPipelineEnabled=0 by default
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of changes
Disables the data pipeline by default
Reason for change
We noticed a potential issue in the settings-update path for data pipelines, that could cause problems if a trace exporter instance is disposed while a request is in flight. Working around the issue requires either a bunch of extra locks (undesirable) or more extensive rework. Rather than risk causing a crash, this PR disables the datapipeline by default temporarily.
Implementation details
Default to
falseinstead of just AASTest coverage
Covered by existing