Add argument to dbt clean for logs
See original GitHub issueDescribe the feature
What are the circumstances in which someone runs dbt clean
? Usually when troubleshooting or trying to understand what is going on that doesn’t look right. When troubleshooting you often want to see your logs to match what you’re looking for. You might look at logs, then run clean, then want run the thing, then look at your logs again. If you forgot to clear or cycle your logs, though, now you might have to dig to find the info you’re looking for.
My proposal: add an argument to dbt clean
that also wipes your logs, e.g. dbt clean --include logs
or something similar.
Describe alternatives you’ve considered
This tip from @clrcrl on cycling logs is what I use: https://discourse.getdbt.com/t/tips-and-tricks-about-working-with-dbt/287/4 but sometimes I forget to run it.
Additional context
Is this feature database-specific? Which database(s) is/are relevant? Please include any other relevant context here.
I don’t think so.
Who will this benefit?
What kind of use case will this feature be useful for? Please be specific and provide examples, this will help us prioritize properly.
Anyone who is troubleshooting dbt models.
Are you interested in contributing this feature?
Let us know if you want to write some code, and how we can help.
👶 🍼 in theory yes, but unlikely
I guess my first question would be: is this something that other people think would be useful in dbt?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top GitHub Comments
oh, interesting. That could work too. Do you see more demand for this?
On Mon, Oct 25, 2021 at 7:41 AM, Jeremy Cohen @.***> wrote:
oh, thanks stale bot for resurfacing this on my radar.