Document workaround for making intentional breaking changes to model with enforced contract #3752
Open
1 task done
Labels
content
Improvements or additions to content
improvement
Use this when an area of the docs needs improvement as it's currently unclear
Contributions
Link to the page on docs.getdbt.com requiring updates
https://docs.getdbt.com/reference/resource-configs/contract#detecting-breaking-changes
What part(s) of the page would you like to see updated?
dbt-labs/dbt-core#7824 (comment)
Available workarounds:
If the breaking contract changes are being made intentionally, an (unsafe!) option is to merge anyways on failing CI -- future CI runs will pass because the baseline state will include the breaking changes. But if that CI run would have failed on something unrelated to contracts after the breaking change check, it would streamroll over a scenario that should have failed.
With what's currently available in dbt, a safer workaround would be to:
Additional information
No response
The text was updated successfully, but these errors were encountered: