fix(test-optimization): no advanced features are enabled if ITR kill … #7141
+0
−24
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.
What does this PR do?
This PR removes a condition that causes the Datadog backend not to be queried for advanced feature settings in case a kill-switch for ITR is provided through the environment variables.
Motivation
In the past, ITR was the only advanced feature, so calling the endpoint to receive feature configuration wasn't necessary with the kill-switch being provided. With more advanced features being added, this causes unwanted side-effects - users might want to toggle off ITR through environment variables but use other features that are being toggled on using the backend request.
In other tracers, this logic was already removed in the past, e.g., dd-trace-py