-
Notifications
You must be signed in to change notification settings - Fork 950
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
Add --quiet
flag docs and print
macro
#1102
Comments
Making a note that this change will come out with dbt-core v1.1.0. |
Thank you @ehmartens and @emmyoop! I've added this to the docs project board! |
@ehmartens Hello! The beta for v1.1 will be cut next week for this. Did you want to draft docs for this? I can review and edit them. One caveat is that we are adding versioning so the docs would need to be encapsulated in versioning code like this:
cc: @jtcohen6 |
Hi @runleonarun ! I'm so sorry for the delay on this. I'm happy to do this tomorrow morning (Us Eastern time) if there is still a need. Let me know! I can have a PR done by Noon US Eastern Time. |
@ehmartens Apologies from me while I try to figure out a process for features created from the dbt community 😄 Anything you could provide would be helpful, even if unpolished. I can clean it up and publish it. |
[Preview](https://docs-getdbt-com-git-dbeatty-print-no-print-dbt-labs.vercel.app/reference/global-configs/print-output#suppress-print-messages-in-stdout) resolves #4776 ## What are you changing in this pull request and why? I checked from v1.7 back to v1.1, and I couldn't get either of these to work in any version: Up to 1.5: ```yaml config: no_print: true ``` 1.5 and after: ```yaml config: print: false ``` However, the `DBT_NO_PRINT` / `DBT_PRINT` environment variables and `--no-print` and `--print` CLI flags _do_ work. So I think the code example for `profiles.yml` was just accidentally introduced in the following PRs, and we should remove it because it's not actually an option for any versions. - #1319 - #3134 For additional context, see: - [Upgrading to v1.1](https://docs.getdbt.com/docs/dbt-versions/core-upgrade/upgrading-to-v1.1#advanced-and-experimental-functionality) - [Upgrading to v1.5](https://docs.getdbt.com/docs/dbt-versions/core-upgrade/upgrading-to-v1.5#behavior-changes) - #1102 - dbt-labs/dbt-core#4701 - #3122 - #3332 ## Checklist - [x] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines. - [x] For [docs versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning), review how to [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content).
Contributions
Link to the page on docs.getdbt.com requiring updates
https://github.com/dbt-labs/docs.getdbt.com/blob/current/website/docs/reference/global-configs.md
https://github.com/dbt-labs/docs.getdbt.com/blob/current/website/docs/reference/dbt-jinja-functions.md
What part(s) of the page would you like to see updated?
I'd like to update the documentation to add info about the new global config that PR-4701 will create. Additionally, I'd like to add documentation for the
print
Jinja function that the PR creates.Additional information
No response
The text was updated successfully, but these errors were encountered: