Feat(sqlmesh_dbt): Add support for --project-dir and --profiles-dir#5524
Merged
Feat(sqlmesh_dbt): Add support for --project-dir and --profiles-dir#5524
Conversation
georgesittas
approved these changes
Oct 10, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds the following CLI arguments to
sqlmesh_dbt:--project-dir- sets the project root, wheredbt_project.ymlis expected to be found, as well as all of the other project files--profiles-dir- sets the directory whereprofiles.ymlis expected to be found, if different from--project-dirNote that due to how Click works, these are currently top-level options because they affect project loading. They currently have to be specified as:
$ sqlmesh_dbt --project-dir /some/dir runrather than what upstream dbt allows:
$ sqlmesh_dbt run --project-dir /some/dirThere are a bunch of other arguments (such as
--target) that also have this problem, i'm planning to refactor this in the next PR to match the behaviour with upstream dbt