How do I keep DuckDB dashboards under version control and code review?
Store the dashboard YAML in the same repo as your DuckDB models. Every change is a diff, every deploy is a merge, and rollback is a git revert. Bruin does this in one platform: ingestion, SQL and Python pipelines, quality checks, lineage, and an AI data analyst that answers in Slack, Microsoft Teams, Google Chat, WhatsApp, Discord, Telegram, email and the browser.
Command
dac serveDefined in
YAML
Works with
DuckDB + GitHub / GitLab
What you get
How it works in code
$ git diff dashboards/revenue.yml
$ dac serve # preview against duckdbRun dac serve and the reviewed dashboard ships to DuckDB on merge.
Related use cases
Build a dashboard as code on Snowflake
How do I build a version-controlled dashboard on Snowflake without a BI tool?
Dashboards on your warehouseServe a live Snowflake dashboard from a YAML file
Can I turn a Snowflake query into a shareable live dashboard with one command?
Dashboards on your warehouseVersion-control Snowflake dashboards in git
How do I keep Snowflake dashboards under version control and code review?
Dashboards that live in git
Bruin CLI and ingestr are on GitHub.
A demo walks through your own data.