Skip to content
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

Clarify the relationship between --quiet and --log-level #4850

Merged
merged 3 commits into from
Feb 2, 2024

Conversation

mirnawong1
Copy link
Contributor

@mirnawong1 mirnawong1 commented Feb 1, 2024

Resolves #4822

adds info about dbt list command and log level warn and quiet to the log page per issue above.

preview

@mirnawong1 mirnawong1 requested a review from a team as a code owner February 1, 2024 17:12
Copy link

vercel bot commented Feb 1, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs-getdbt-com ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 2, 2024 1:14am

@github-actions github-actions bot added content Improvements or additions to content size: small This change will take 1 to 2 days to address Docs team Authored by the Docs team @dbt Labs labels Feb 1, 2024
Copy link
Collaborator

@runleonarun runleonarun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @mirnawong1 some small suggestions. Feel free to edit my edits!

website/docs/reference/global-configs/logs.md Outdated Show resolved Hide resolved
website/docs/reference/global-configs/logs.md Outdated Show resolved Hide resolved

In [dbt version 1.5](/docs/dbt-versions/core-upgrade/upgrading-to-v1.5#behavior-changes), there have been changes to the logging behavior of the [dbt list](/reference/commands/list) command. In version 1.5, the default behavior has been updated, and it now includes `INFO` level logs by default

Previously, the list command (and only the list command) had `WARN`-level stdout logging, to support piping its results to [`jq`](https://jqlang.github.io/jq/manual/), a file, or another process.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this ☝🏻 paragraph if we move the bits about piping results to the next paragraph?

website/docs/reference/global-configs/logs.md Outdated Show resolved Hide resolved
Copy link
Collaborator

@runleonarun runleonarun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@runleonarun runleonarun enabled auto-merge (squash) February 2, 2024 01:04
@runleonarun runleonarun merged commit 092c74a into current Feb 2, 2024
7 checks passed
@runleonarun runleonarun deleted the add-quiet-log-evel branch February 2, 2024 01:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content Docs team Authored by the Docs team @dbt Labs February-2024 size: small This change will take 1 to 2 days to address
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify the relationship between --quiet and --log-level
2 participants