npm and yarn and many other tools turn off telemetry on CI servers by default. Partially to reduce the time to run and partially because CI tends to handle IP and secrets.
az has the ability to turn off telemetry explicitly by calling
az config set collect_telemetry=false --only-show-errors
There are a few other settings that are reccomended by the az-cli team through the az init extension:
az config set auto-upgrade.enable=false --only-show-errors
az config set core.error_recommendation=off --only-show-errors
az config set core.disable_progress_bar=true --only-show-errors
az config set core.no_color=true --only-show-errors
az config set output.show_survey_link=no --only-show-errors
az config set logging.enable_log_file=no --only-show-errors
I propose az-cli should adopt these settings by default, unless explicitly configured otherwise when it detects a CI environment.
It could use similar features as the is-ci node module or Python-vw.
npmandyarnand many other tools turn off telemetry on CI servers by default. Partially to reduce the time to run and partially because CI tends to handle IP and secrets.azhas the ability to turn off telemetry explicitly by callingThere are a few other settings that are reccomended by the
az-cliteam through theaz initextension:I propose
az-clishould adopt these settings by default, unless explicitly configured otherwise when it detects a CI environment.It could use similar features as the
is-cinode module or Python-vw.