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.

Sign up for GitHub

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

Update --favor-state note #6648

Merged
merged 4 commits into from
Dec 16, 2024
Merged

Update --favor-state note #6648

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c90baff
Update about in --favor-state Note
marcelobour Dec 12, 2024
da930d4
Merge branch 'current' into patch-1
mirnawong1 Dec 13, 2024
8e54711
Update website/docs/docs/cloud/about-cloud-develop-defer.md
mirnawong1 Dec 16, 2024
aec0981
Merge branch 'current' into patch-1
mirnawong1 Dec 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/docs/docs/cloud/about-cloud-develop-defer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ When using `--defer`, dbt Cloud will follow this order of execution for resolvin
2. If a development version doesn't exist, dbt uses the staging locations of parent relations based on metadata from the staging environment.
3. If both a development and staging version doesn't exist, dbt uses the production locations of parent relations based on metadata from the production environment.

**Note:** Passing the `--favor-state` flag will always resolve refs using production metadata, regardless of the presence of a development relation, skipping step #1.
**Note:** Passing the `--favor-state` flag will always resolve refs using staging metadata if available; otherwise, it defaults to production metadata regardless of the presence of a development relation, skipping step #1.

For a clean slate, it's a good practice to drop the development schema at the start and end of your development cycle.

Expand Down
Loading