DO_NOT_TRACK=0
is not the same as DBT_SEND_ANONYMOUS_USAGE_STATS=True
#4713
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you changing in this pull request and why?
While responding to dbt-labs/dbt-core#9336, I set
DO_NOT_TRACK=0
and examined the result. It does not behave the same way asDBT_SEND_ANONYMOUS_USAGE_STATS=True
.Looking at the source code here explains why.
So we can safely just remove this line from the docs for
send_anonymous_usage_stats
to avoid confusion.Additional info
We first added support for the Console Do Not Track initiative within dbt-labs/dbt-core#5000 as described in dbt-labs/dbt-core#3540.
Any of the following are equivalent to
DBT_SEND_ANONYMOUS_USAGE_STATS=False
(whether they are uppercase, lowercase, or mixed case):Any other values of
DO_NOT_TRACK
are ignored altogether and not have any effect.Checklist