-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
dbt clean does not respect the project-dir if provided #2840
Labels
bug
Something isn't working
good_first_issue
Straightforward + self-contained changes, good for new contributors!
Comments
Good find, @feluelle! I'm not sure if this has worked in the past, but I agree it's the intended (and expected) behavior. I'm hopeful that this would be a straightforward fix, involving the addition of Is this something you'd be interested in contributing? |
jtcohen6
added
good_first_issue
Straightforward + self-contained changes, good for new contributors!
and removed
triage
labels
Oct 19, 2020
Yes, I would love to work on that @jtcohen6 :) |
4 tasks
feluelle
added a commit
to feluelle/dbt
that referenced
this issue
Oct 20, 2020
feluelle
added a commit
to feluelle/dbt
that referenced
this issue
Oct 21, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
good_first_issue
Straightforward + self-contained changes, good for new contributors!
Describe the bug
If I am not in the project directory and run
dbt clean --project-dir <path>
. DBT won't clean the directories starting from the project directory. It cleans it from the current directory.Steps To Reproduce
go out of the project directory and pass the path to directory to the
--project-dir
flag.Expected behavior
I expect dbt to clean the directories recursively defined in
clean-targets
ofdbt_project.yml
.System information
Which database are you using dbt with?
The output of
dbt --version
:The operating system you're using: macOS 10.15.6
The output of
python --version
: Python 3.7.2The text was updated successfully, but these errors were encountered: