Feature: Block all dbt-loom related telemetry by default. Allow for an opt-in #97
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.
Description and Motivation
Currently,
dbt-core
's built-in telemetry reports on all dbt plugins loaded and the number of upstream models and packages injected. This type of telemetry presents a conflict of interest since dbt Labs' cloud offering is designed to be the "de facto" way to manage multi-project deployments, and they have a vested interest to identify and sell pricey enterprise contracts todbt-loom
users.In an effort to provide a layer of privacy to
dbt-loom
users, this PR patches thedbt-core
track
method such that all messages that referencedbt-loom
are quietly dropped and not reported to dbt Lab's Snowplow instance. This does not impact any other function ofdbt-core
(including other telemetry!) ordbt-loom
.If a user wants to provide this telemetry data, they can re-enable it by adding
enable_telemetry: true
to the projectdbt_loom.config.yaml
file.Resolves: #92