Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add plugin option "use project dir for profiles"
See original GitHub issueIf you work with many DBT projects on different envs/machines it is much more convenient to keep profiles.yml file in each project folder. However the extension doesn’t support this kind of configuration (or I can’t find that option at least).
Is there any chance to add plugin settings like “use project dir for profiles” and if this option has been chosen then plugin will be adding smth. like --profiles-dir $PWD to any DBT command from its scope to show models, dependencies, to run models etc.?
Issue Analytics
- State:
- Created a year ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Doesn’t work for me. I’ve added
"dbt.profilesDirOverride": ".", but extension still can’t find theprofiles.ymlI have a similar issue where dbt.profilesDirOverride does not seem to resolve relative paths. It is able to resolve absolute paths but this can be an issue when you plan on sharing the workspace settings with a team