-
Notifications
You must be signed in to change notification settings - Fork 243
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allow controlling telemetry via the
ODO_TRACKING_CONSENT
environmen…
…t variable (#6258) * Add support for ODO_TRACKING_CONSENT env variable Co-authored-by: Armel Soro <asoro@redhat.com> * Replace deprecated 'ODO_DISABLE_TELEMETRY' env var with 'ODO_TRACKING_CONSENT' in integration tests * Log environment of process launched with 'helper_run' in integration tests `odo` behavior might be altered based on certain environment variables. So this is to help debug future issues that might happen. Because the process environment also contains the current OS environment, we purposely limit the content to variables prefixed with 'ODO_' or particular ones (like 'TELEMETRY_CALLER'). * Test conflicting situations when using both 'ODO_DISABLE_TELEMETRY' and 'ODO_TRACKING_CONSENT' * Disable golangci-lint 'staticcheck' check about using the deprecated 'segment.DisableTelemetryEnv' However, due to [1], line-based directives do not seem to be working. * Make ODO_TRACKING_CONSENT env var take precedence over the ConsentTelemetry preference See [1] for more context. [1] https://github.com/redhat-developer/odo/pull/6258\#issuecomment-1293736398 * Add new 'segment#isTrackingConsentEnabled' function, as suggested in review This would make it easier to rename the values if needed or add aliases later. * Add more unit test cases, especially when any of the telemetry var is not there in the env * Document ODO_TRACKING_CONSENT * fixup! Add new 'segment#isTrackingConsentEnabled' function, as suggested in review * fixup! fixup! Add new 'segment#isTrackingConsentEnabled' function, as suggested in review Co-authored-by: Tomas Kral <tkral@redhat.com>
- Loading branch information
Showing
11 changed files
with
403 additions
and
155 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.