Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release/v0.2.0 #47

Merged
merged 22 commits into from
Jan 5, 2022
Merged

Release/v0.2.0 #47

merged 22 commits into from
Jan 5, 2022

Conversation

jakeberesford-palmetto
Copy link
Collaborator

Release PR v0.2.0 -> main

emekdahl-palmetto and others added 22 commits December 3, 2021 11:04
Update develop with release items from main
Running dbt deps all the time is slow and error prone (if dbt hub is down, or there is a github outage).
Forgetting to run dbt deps can also cause confusing errors.
By changing our baseline implementation to assume dbt deps is run in the docker image,
we can avoid these problems.

The --deps option has been added to every relevant command
this allows a user to specify they want to run deps with a given command

* Also refactored some nasty conditional branching in cmd_cycle
All commands are fast once dbt clean && deps happens in the image!
Run dbt deps after dbt clean as we will always need to re-instlal deps at this point
just use a condition in make_cmd to prevent appending
an empty string when --persist is set
docker-compose.yaml template

* Includes logic to detect configured changes to the default location for dbt_modules
…eloper should rebuild the image with palm build
…n-image-by-default

Feature/dbt deps in image by default
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants