Fix --check behavior when --dry-run is used#316
Open
ththicn wants to merge 1 commit intoz3z1ma:mainfrom
Open
Conversation
This file contains hidden or 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
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.
Hi maintainers, this is my first contribution, please let me know if anything should be changed in the approach, style, or tests. 🙏
When the --check flag was used with the --dry-run flag, the exit status was 0 even if there were changes in schema.yml. I made it so that mutation_tracker is called even when the --dry-run flag is passed.
Test
Preparation
Add a new column to the
stg_ordersmodel.$ git diff demo_duckdb/models/staging/stg_orders.sql diff --git a/demo_duckdb/models/staging/stg_orders.sql b/demo_duckdb/models/staging/stg_orders.sql index a654dcb..bc0f31b 100644 --- a/demo_duckdb/models/staging/stg_orders.sql +++ b/demo_duckdb/models/staging/stg_orders.sql @@ -14,8 +14,8 @@ renamed as ( id as order_id, user_id as customer_id, order_date, - status - + status, + 'new_column' as new_column from source )Build the deme_duckdb project
Testing dbt-osmosis
Before fixing
Changes exist, but exit status is 0.
After fixing