Slide 1 of 4

CI/CD pipeline architecture

CI/CD pipeline flow

You can commit dashboard JSON by hand after every SDK change, but that still depends on someone remembering to regenerate and push. A CI/CD pipeline removes that bottleneck.

This diagram shows one end-to-end flow from code change to a live dashboard when Git Sync is already connected to the repository.

Diagram showing CI/CD pipeline: on pull request, code flows through generate, JSON check, and PR review; on merge to main, Git Sync updates Grafana

What each stage does

StageTriggerAction
GenerateEvery push and pull requestRun Foundation SDK code and produce dashboard JSON
JSON check / reviewPull requestConfirm the generated JSON is what the PR intends to merge (for example fail if committed files are out of date)
Git SyncAfter merge to the synced branchGrafana polls or receives a webhook and updates provisioned dashboards from Git

When each path runs

  • On a pull request: the pipeline regenerates JSON and gives reviewers a chance to inspect the file changes before merge. Nothing needs to talk to the Grafana API for that review gate.
  • On merge to main (or whichever branch Git Sync watches): the merged JSON is in the repository, and Git Sync brings Grafana in line with Git.

The Foundation SDK still only generates files. Git Sync remains the sync step you set up in Grafana.

Next