dbt Core

dbt

dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications.

Detected by dbt | macOS, Linux, Windows |www.getdbt.com

Sync it dbt.toml

Sync rules

What travels, what stays, what never leaves

dbt Core in your home directory Every rule on this page, by file

…

method: service-account

project: example-analytics

dataset: dbt_octocat

keyfile: /Users/octocat/Downloads/example-analytics-a1b2c3.jsonmachine-local

location: us-east1

threads: 4

lakehouse:

…

Each machine keeps its own copy of these.

*.outputs.*.password*.outputs.*.private_key*.outputs.*.private_key_passphrase*.outputs.*.token

Lifted into your secret store; the rest of the file syncs.

· .user.yml Exclude

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/dbt.tomlThe file this page is generated from

id = "dbt"

name = "dbt Core"

homepage = "https://www.getdbt.com"

description = "dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications."

icon = "theSVG:dbt"

detect = ["dbt"]

# https://docs.getdbt.com/docs/core/connect-data-platform/connection-profiles

# — "profiles.yml lives in the ~/.dbt/ directory by default", one file shared

# by every project on the machine ($DBT_PROFILES_DIR overrides it).

paths = ["~/.dbt/profiles.yml"]

# ~/.dbt/.user.yml is the anonymous id dbt sends with usage stats. It

# identifies this installation, not the user's configuration:

# https://docs.getdbt.com/reference/global-configs/usage-stats

exclude = ["~/.dbt/.user.yml"]

# profiles.yml is not a whole-file secret: targets, schemas, warehouses,

# thread counts and the target selection are exactly what a second machine

# needs. The credentials are lifted out below.

secret = []

# Read at the start of each invocation; the process exits with the run.

side_effect = false

# The warehouse credentials, taken from the adapter setup pages: password

# (Postgres, Redshift, Snowflake), private_key and private_key_passphrase

# (Snowflake key-pair auth) and token (Databricks, Snowflake SSO).

# https://docs.getdbt.com/docs/core/connect-data-platform/snowflake-setup

[[secret_paths]]

file = "~/.dbt/profiles.yml"

match = { key_path = ["*.outputs.*.password", "*.outputs.*.private_key", "*.outputs.*.private_key_passphrase", "*.outputs.*.token"] }

# BigQuery's service-account keyfile is an absolute path to a JSON key sitting

# on this disk — the setup page's own example is a path under

# /Users/youruser/Downloads. The file it points at does not travel, so the

# line pointing at it must not either — but where this machine keeps its

# service-account key is something the user has to put back after a rebuild,

# so it is kept: backup.

# https://docs.getdbt.com/docs/core/connect-data-platform/bigquery-setup

[[machine_lines]]

file = "~/.dbt/profiles.yml"

match = { key_path = ["*.outputs.*.keyfile"] }

scope = "backup"

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/dbt. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these is generated from the same rules as this page. None of them splits *.outputs.*.keyfile for you — that part is Otty’s own sync, or a template you write by hand.