ROX-33862: fix ignored explicit telemetry key#19651
ROX-33862: fix ignored explicit telemetry key#19651parametalol wants to merge 2 commits intomasterfrom
Conversation
|
Skipping CI for Draft Pull Request. |
|
Images are ready for the commit at 7d9a62d. To use with deploy scripts, first |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #19651 +/- ##
==========================================
+ Coverage 49.37% 49.39% +0.02%
==========================================
Files 2742 2745 +3
Lines 206953 207228 +275
==========================================
+ Hits 102187 102369 +182
- Misses 97182 97267 +85
- Partials 7584 7592 +8
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@parametalol: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Description
When a telemetry storage key is explicitly provided (e.g. via
ROX_TELEMETRY_STORAGE_KEY_V1), theReconfiguremethod was overwriting it with the key fetched from the remote configuration endpoint. This caused explicitly configured environments to lose their intended key.The fix skips updating the storage key from remote config when an explicit key was provided, unless the remote key is
DISABLED— which must always take effect to allow telemetry to be shut down remotely.User-facing documentation
Testing and quality
Automated testing
How I validated my change
eventual.Valueblocking.