How do I stop bad data from reaching production tables?
Mark checks as blocking. When a blocking check fails, Bruin halts the run before the downstream models build, so bad data never propagates.
Command
bruin runDefined in
YAML + SQL
Works with
Bruin CLI + your warehouse
What you get
Custom SQL checksblocking gatesCI-friendly
How it works in code
custom_checks:
- name: no_future_dates
query: SELECT count(*) FROM orders WHERE created_at > now()Run bruin run and the run fails the moment the rule is violated.
Related use cases
Custom checks and gates
Write a custom SQL quality check
How do I write a custom check with my own SQL?
Custom checks and gatesWarn without failing on a soft check
Can I get a warning without failing the whole run?
Custom checks and gatesEnforce a data contract between teams
How do I enforce a schema contract on data another team produces?
Catch bad data before it ships
Open source. Built-in and custom checks that run on every pipeline run.