GitHub action for `lightdash deploy` should work even if my dbt project isn't in my root directory
See original GitHub issueDescription
Right now, if I have a dbt project that I’m trying to connect our lightdash deploy
GitHub action to and it’s not in the root repo (i.e. it’s in my-repo/dbt/models
instead of dbt/models
), then I get this error:
invalid project dir
We should add some default folders, or use a find script to locate the yaml file inside the repo so that this error doesn’t happen.
Issue Analytics
- State:
- Created a year ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
new project creation fails when dbt folders are not in root #1414
Describe the bug I have modified my ./dbt_profiles.yml config to group all dbt folders in a subfolder model-paths: [ "dbt/models" ] ...
Read more >How to Deploy dbt to Production using GitHub Actions
Setup a dbt profile for GitHub Actions Create a profiles. yml file at the root of your repository. Every time it runs, dbt...
Read more >Sync your changes with Lightdash deploy | Documentation
lightdash deploy syncs the changes in your dbt project to Lightdash. ... If you've connected Lightdash to GitHub, you can setup a github...
Read more >Scheduling dbt Core with Github Actions - DEV Community
I have been using dbt more and more as my main tool for data ... Create .github/workflows/ directory in the root of your...
Read more >dbt at scale on Google Cloud - Part 3
As always, deploy your resource via Terraform and you have to use the google_composer_environment. Deployment of Cloud Composer in fully private mode with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@rephus that looks good 👍 I would go with that right now and ignore the cases of multiple dbt projects in the same repo.
Tested option 5 https://github.com/rephus/dbt_solar_panels/actions/runs/3158347054/jobs/5140278661
on root https://github.com/rephus/dbt_solar_panels/actions/runs/3158376058/jobs/5140339939