-
Notifications
You must be signed in to change notification settings - Fork 108
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
Use print
instead of log
#56
Comments
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days. |
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers. |
Can this be re-opened? As far as I can tell there's still no easy way to feed the output of |
@pdfrod there's actually an open PR (linked above) which actions this which I'm trying to nudge towards a merge/release! |
Describe the feature
Rather than using the
log
Jinja function to output generated code, use theprint
Jinja function added in PR-4701Describe alternatives you've considered
Leave as-is.
Additional context
This isue is based on a suggestion from @emmyoop (here) to allow for cleaner output from the macros using the new global
--quiet
flag in dbt.@jaypeedevlin and I worked on PR-4701 together to implement the solution she outlined in
dbt-core
, and would like to complete this next part of it as well.Who will this benefit?
Users who would like to copy the output from
dbt run-operation
directly into a file without having to remove info and warnings.Are you interested in contributing this feature?
Yep!
The text was updated successfully, but these errors were encountered: