Slide 1 of 3

Key takeaways

Principles to remember

  1. Dashboards deserve Infrastructure as Code rigor. Version control, review, and automation produce a solid dashboarding experience.
  2. Strong typing catches errors early. Broken configuration fails at compile time, not in production.
  3. Stable UIDs enable idempotent deploys. Same UID means update, not duplicate.
  4. The pipeline is the source of truth. Code on main equals what’s deployed.

Script

Four principles to take with you.

First, dashboards deserve the same rigor as infrastructure. Version control, code review, automated deployment. If you do it for servers, do it for dashboards.

Second, the Foundation SDK catches errors before deployment. Strong typing means broken dashboards fail at compile time, not in production.

Third, stable UIDs are what make deployments idempotent. Always set a UID in your DashboardBuilder. It’s the difference between updating a dashboard and creating duplicates.

Fourth, the pipeline is the source of truth. Once you have CI/CD in place, the code on main is always what’s deployed. Manual edits get corrected on the next run.

Next