Update global configs for v 1.1 #1319
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for docs-getdbt-com ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
@gwenwindflower I'm not sure if you wanted to add any context, or does my example provide enough info? |
jtcohen6
reviewed
Apr 12, 2022
* adding the select cache resource 1st draft * add warning * add version * Update website/docs/reference/global-configs.md * adding exmple Co-authored-by: runleonarun <leona@dbtlabs.com>
jtcohen6
requested changes
Apr 13, 2022
Co-authored-by: Jeremy Cohen <jeremy@dbtlabs.com>
jtcohen6
reviewed
Apr 14, 2022
Co-authored-by: Jeremy Cohen <jeremy@dbtlabs.com>
|
I got a verbal OK to merge from Jeremy, so merging now! |
2 tasks
mirnawong1
added a commit
that referenced
this pull request
Jan 23, 2024
[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).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #1102
Description & motivation
This PR:
Pre-release docs
Is this change related to an unreleased version of dbt?
currentChecklist
If you added new pages (delete if not applicable):
website/sidebars.jsIf you removed existing pages (delete if not applicable):
website/sidebars.js_redirects