graphql-engine
graphql-engine copied to clipboard
Unable to disable "telemetry" popup
Version Information
Server Version: 2.1.1
Environment
OSS
What is the expected behaviour?
When telemetry is disabled through an environment variable, I should haven't to deal with the Telemetry popup.
What is the current behaviour?
It's not clear whether or not Telemetry is disabled because the popup still comes up when logging into the Hasura console.
How to reproduce the issue?
- Start Hasura with HASURA_GRAPHQL_ENABLE_TELEMETRY: "false"
- Enable console with HASURA_GRAPHQL_ENABLE_CONSOLE: "true"
- Notice the telemetry popup in the console, that suggests Telemetry is enabled
Screenshots or Screencast
actually @rikinsk this also applies to the CLI tool. If I disable telemetry at the docker image level, I also expect the CLI tool not to nag me everytime I run it.
Worse is I get the INFO message even though I run with log-level WARN
For example
docker run --net=host --rm -d --name hasura \
-e HASURA_GRAPHQL_DATABASE_URL=postgresql://XXX?application_name=hasura \
-e HASURA_GRAPHQL_ENABLE_CONSOLE=false \
-e HASURA_GRAPHQL_ENABLE_TELEMETRY=false \
-v "$PWD/../hasura/":/migrations \
hasura/graphql-engine:v2.9.0.cli-migrations-v2
docker exec -i hasura hasura-cli migrate apply --skip-update-check --log-level WARN --skip-execution --up all --project /migrations
...
{"level":"info","msg":"Help us improve Hasura! The cli collects anonymized usage stats which\nallow us to keep improving Hasura at warp speed. To opt-out or read more,\nvisit https://hasura.io/docs/latest/graphql/core/guides/telemetry.html\n","time":"2022-08-09T00:19:20Z"}