-
Notifications
You must be signed in to change notification settings - Fork 44
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 v1.2.1: Env var name collision with dbt-core #39
Comments
I've opened a pr for it --> #40 |
Thank you both! When I created this action I wanted to capture the actual screen output, hence the @joelazar I am still getting around to testing this myself, but did you test your PR that just renaming for now does the trick? |
@mwhitaker, yes, and it did the trick :) |
Thank you! Merged #40 |
With the latest release, actions have begun to fail due to misconfiguration of logging.
It seems that dbt-core expects that the new
DBT_LOG_PATH
env var (also available as the log-path yml config) points to a directory. However, theDBT_LOG_PATH
in dbt-action seems to serve different purpose at points at the log file itself..Perhaps the
DBT_LOG_PATH
env var in dbt-action is no longer necessary given the new dbt-core log-path config option? Happy to submit a PR if you are accepting them right now! 🙂The text was updated successfully, but these errors were encountered: