#How to use DO_NOT_TRACK with dagger
1 messages · Page 1 of 1 (latest)
Hey, @zenith lily
Are you connected to dagger cloud from dagger login?
yeah I am. and I did verify if I logout, it does not send traces anymore. but I was hoping there is an env variable or config to disable for one tool (think of it like a private repo), while I can keep it for another tool (vs public repo).
Hey Rajat! DO_NOT_TRACK is for the CLI analytics, not cloud metrics. Try setting DAGGER _CLOUD_TOKEN to "" and check if that helps please
hey Marcos 👋 , let me try that. thanks
hmm, that didn't help. I may be doing something incorrectly, i will come back to this later in the day and try again.
My comment above was a guess. Let me try really quick
@zenith lily just checked that a quick way to bypass this is by setting XDG_CONFIG_HOME to a bogus directory. i.e: XDG_CONFIG_HOME=/tmp/foo dagger call.. won't read any dagger config files
👍 thank you very much for checking this out Marcos. I will try this out and let you know.