How do I keep pipeline definitions consistent across the team?
Add validation and naming checks to CI. Pipelines that do not meet the standard fail the check before they merge.
Command
bruin runDefined in
YAML + CI
Works with
CI + Bruin CLI
What you get
CI validationgated deploysgit rollback
How it works in code
# .github/workflows/data.yml
- run: bruin validate ./pipeline
- run: bruin run ./pipelineRun bruin run and your data pipelines follow the same review and deploy path as your app.
Related use cases
Ship data pipelines like software
Open source. Validate in CI, gate on checks, deploy on merge, roll back with git.