root
/
grafana
mirror of https://github.com/grafana/grafana.git
1
0
Fork 0
Code Issues Actions 31 Packages Projects Releases Wiki Activity
grafana/pkg/registry/apis/dashboard/legacy
History
Stephanie Hingtgen 0cef2b9ae7
Dashboard Versions: Make compatible with app platform (#99327) 		2025-01-28 08:17:52 -06:00
..
testdata Dashboard Versions: Make compatible with app platform (#99327) 2025-01-28 08:17:52 -06:00
README.md
…
client.go Search: Remove history query (#99026) 2025-01-15 12:49:47 -06:00
context.go K8s/Dashboards: Pass the legacy internal ID into labels (#98311) 2024-12-20 21:33:49 +02:00
queries.go LibraryPanels: Expose library panels in dashboard apiserver (#92213) 2024-08-27 12:12:22 +03:00
queries_test.go Dashboards/SQL: Improve SQL query behavior (#99253) 2025-01-21 19:35:33 +03:00
query_dashboards.sql Dashboard Versions: Make compatible with app platform (#99327) 2025-01-28 08:17:52 -06:00
query_panels.sql LibraryPanels: Expose library panels in dashboard apiserver (#92213) 2024-08-27 12:12:22 +03:00
sql_dashboards.go Dashboard Versions: Make compatible with app platform (#99327) 2025-01-28 08:17:52 -06:00
storage.go Dashboard Versions: Make compatible with app platform (#99327) 2025-01-28 08:17:52 -06:00
token.go
…
types.go Dashboards/SQL: Improve SQL query behavior (#99253) 2025-01-21 19:35:33 +03:00

README.md

This implements a ResourceServer backed by the existing dashboard SQL tables.

There are a few oddities worth noting. This is not a totally accurate implementation, but it is good enough to drive the UI needs and let kubectl list work!

  1. The resourceVersion is based on internal ID and dashboard version
  • can get version from the least significant digits
  • avoids duplicate resourceVersions... but not sequential
  • the resourceVersion is never set on the list commands
  1. Results are always sorted by internal id ascending
  • this ensures everything is returned