opensource/grafana
1
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-07-30 03:22:29 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
grafana/pkg/registry/apis/dashboard/legacy
History
Mustafa Sencer Özcan c47fc53eee fix: set withHistory flag to true for non-interactive mode (#107263)
2025-06-26 16:08:30 +00:00
..
testdata
fix: set withHistory flag to true for non-interactive mode (#107263)
2025-06-26 16:08:30 +00:00
client.go
refactor(unified-storage): move generated protos to own pkg (#105356)
2025-05-15 21:36:52 +02:00
context.go
K8s/Dashboards: Pass the legacy internal ID into labels (#98311)
2024-12-20 21:33:49 +02:00
legacy_migrator_mock.go
refactor(unified-storage): move generated protos to own pkg (#105356)
2025-05-15 21:36:52 +02:00
migrate.go
chore: add logging around migration cli (#107046)
2025-06-20 15:20:06 +00:00
queries_test.go
SQLTemplates: Add helper to ensure all templates have a test-case (#103964)
2025-04-22 11:21:51 +02:00
queries.go
K8s/Dashboard/SQL: Support ascending order query (#101363)
2025-02-28 11:34:09 +03:00
query_dashboards.sql
fix: set withHistory flag to true for non-interactive mode (#107263)
2025-06-26 16:08:30 +00:00
query_panels.sql
…
README.md
…
sql_dashboards_test.go
K8s/Dashboard: Promote from alpha1 to beta1 (#104009)
2025-04-23 20:54:35 +03:00
sql_dashboards.go
K8s: Dashboards /apis: Fix library element connections (#106734)
2025-06-13 21:40:39 +02:00
storage_test.go
refactor(unified-storage): move generated protos to own pkg (#105356)
2025-05-15 21:36:52 +02:00
storage.go
unistore: split ListIterator and ListHistory in StorageBackend (#105654)
2025-05-23 15:00:18 +02:00
token.go
…
types.go
refactor(unified-storage): move generated protos to own pkg (#105356)
2025-05-15 21:36:52 +02: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