Repository navigation
fix: disable Segment telemetry in E2E deployments - #184
Merged
Merged
Conversation
Signed-off-by: Tomas Kral <tkral@redhat.com> Assisted-by: Codex
This was referenced Oct 9, 2026
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
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 changed
RHDH instances deployed by the E2E utilities now receive
SEGMENT_TEST_MODE=truethrough the sharedrhdh-secretsSecret. This prevents test traffic from reaching production Segment/Amplitude analytics when a release image contains a production write key. A workspace can override the default for an analytics test that uses a dummy key.Bump the utilities package to 2.2.4 and document the default.
Validation
yarn check(passed; existing lint warnings only)yarn build(passed; built Secret contains the new value)yarn test(277 passed)related: https://redhat.atlassian.net/browse/RHDHBUGS-3923