Profiles yml precedence core fusion #8443
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Update _profiles.yml.md to show precedence order with tabs for Core vs Fusion - Update _connection-profiles.md to clarify differences in profile directory precedence - Add note that DBT_PROFILES_DIR is only supported in dbt Core, not Fusion - Clarify that Fusion uses a simplified precedence without DBT_PROFILES_DIR env var Co-authored-by: mirna.wong <[email protected]>
|
Cursor Agent can help with this pull request. Just |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
bot
added
content
mirnawong1
commented
Jan 16, 2026
| dbt Fusion determines the parent directory for `profiles.yml` using the following precedence: | ||
|
|
||
| 1. `--profiles-dir` option | ||
| 2. current working directory |
mirnawong1
commented
Jan 16, 2026
| dbt Fusion searches for the parent directory of `profiles.yml` in the following order and uses the first location it finds: | ||
|
|
||
| 1. `--profiles-dir` flag — Override for CI/CD or testing. | ||
| 2. Project root directory (current working directory) — Project-specific credentials. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
This PR updates the documentation for
profiles.ymlprecedence on both theprofiles.ymlandconnection-profilespages.The changes clarify the different precedence orders for
profiles.ymllocation between dbt Core and dbt Fusion. Specifically, it highlights that theDBT_PROFILES_DIRenvironment variable is only supported in dbt Core and not in dbt Fusion.This addresses user confusion regarding
profiles.ymlresolution in Fusion environments, as discussed in this Slack thread.Checklist
Slack Thread