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

[Core] Order of precedence for project flags, environment variables, and CLI flags #5636

Open
dbeatty10 opened this issue Jun 10, 2024 · 0 comments
Labels
content Improvements or additions to content dbt Core The changes proposed in this issue relate to dbt Core size: medium This change will take up to a week to address

Comments

@dbeatty10
Copy link
Contributor

Link to the page(s) on docs.getdbt.com requiring updates

These pages are all related:

Tell us more about this update

It would be great if:

  1. All three of these pages cross-link to each other
  2. There were a common snippet across all three of these pages that explains the precedence order

The snippet could be similar / same as here.

Or it could be something as simple as this:

Config precedence

dbt will pick the config in the following order (lower takes priority):

  1. project flags
  2. environment variable
  3. CLI flag

i.e., if all three are provided, then the CLI flag takes precedence.

Reviewers/Stakeholders/SMEs

Me :sunglasse

Related GitHub issues

Came up most recently here:

Additional information

Related to these issues:

@dbeatty10 dbeatty10 added content Improvements or additions to content dbt Core The changes proposed in this issue relate to dbt Core labels Jun 10, 2024
@nataliefiann nataliefiann added the size: medium This change will take up to a week to address label Sep 17, 2024
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 dbt Core The changes proposed in this issue relate to dbt Core size: medium This change will take up to a week to address
Projects
None yet
Development

No branches or pull requests

2 participants