Use an existing dbt profile¶
If you already have a profiles.yml somewhere — ~/.dbt/, a shared
config repo, or alongside an existing dbt project — tycoon will pick it
up without copying or rewriting anything.
TL;DR¶
# 1. Tell tycoon where the profile lives (only if it's not co-located).
tycoon register dbt /path/to/your/dbt-project --profiles-dir ~/dbt-config
# 2. Verify what tycoon resolved.
tycoon profiles list
tycoon profiles doctor
# 3. Run as normal — tycoon shells out to dbt with the right --profile /
# --profiles-dir / --target every time.
tycoon data transform build
Resolution order¶
Same as dbt's own CLI, so nothing surprising:
--profiles-dir/--profile/--targeton the tycoon command.dbt_profiles_dir/dbt_profile/dbt_targetintycoon.yml.<dbt_project_dir>/profiles.yml(dbt 1.5+ co-located).$DBT_PROFILES_DIR.~/.dbt/profiles.yml.
The first one that contains the requested profile wins. Tycoon never
copies, edits, or rewrites your profiles.yml — it only reads from it.
Common scenarios¶
"My profile lives under ~/.dbt"¶
Nothing to do. tycoon profiles list will find it automatically.
"My profile lives in a shared config repo"¶
Persist the path in tycoon.yml:
Or pass --profiles-dir per command:
"I want to run a one-off against prod"¶
Doesn't touch tycoon.yml. The next invocation falls back to the default
target.
"Different profiles for dev and CI"¶
Two ways:
- Set
dbt_profile: civia env-awaretycoon.yml(use${VAR}interpolation). - Or pass
--profile cifrom your CI pipeline.
Validating before you run¶
tycoon profiles doctor
# ✓ Found profiles.yml: /Users/me/.dbt/profiles.yml (via ~/.dbt/profiles.yml)
# ✓ Active profile: analytics (target: dev)
# ✓ Adapter: snowflake
# → snowflake://acct123/ANALYTICS_DB
# ✓ Adapter matches stack.warehouse (snowflake).
The doctor check catches the most common foot-gun: tycoon.yml declares
stack.warehouse: duckdb but the active profile actually points at
Snowflake. tycoon doctor runs the same check and reports it
non-fatally alongside the rest of your environment.
What about secrets?¶
tycoon profiles show redacts known secret-bearing fields (password,
private_key, token, client_secret, api_key, etc.) before
printing. The original profiles.yml is never modified.
Use ${VAR} env-var interpolation in your profiles.yml and source the
values from .env or the shell — tycoon doesn't add any new way to
configure secrets, it just reads dbt's existing one.