The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
grafana/pkg/registry/apis/dashboard/legacy
Stephanie Hingtgen 745015e74f
[release-12.0.1] K8s: Dashboards: Fix provisioned dashboard cleanup (#104504) (#104525)
3 months ago
..
testdata K8s: Dashboards: Reduce db calls to get users on list (#103020) 4 months ago
README.md K8s/Dashboards: Implement dashboards as StorageBackend (#90295) 1 year ago
client.go K8s: Remove restore functionality; can be done with list (#102560) 4 months ago
context.go K8s/Dashboards: Pass the legacy internal ID into labels (#98311) 7 months ago
legacy_migrator_mock.go Provisioning: add most mocks to unit test provisioning jobs (#103446) 4 months ago
migrate.go [release-12.0.1] K8s: Dashboards: Mark as v1beta1 (#104422) 3 months ago
queries.go K8s/Dashboard/SQL: Support ascending order query (#101363) 5 months ago
queries_test.go K8s/Dashboard/SQL: Support ascending order query (#101363) 5 months ago
query_dashboards.sql K8s: Dashboards: Reduce db calls to get users on list (#103020) 4 months ago
query_panels.sql LibraryPanels: Expose library panels in dashboard apiserver (#92213) 11 months ago
sql_dashboards.go [release-12.0.1] K8s: Dashboards: Fix provisioned dashboard cleanup (#104504) (#104525) 3 months ago
sql_dashboards_test.go [release-12.0.1] K8s: Dashboards: Mark as v1beta1 (#104422) 3 months ago
storage.go [release-12.0.1] K8s: Dashboards: Mark as v1beta1 (#104422) 3 months ago
storage_test.go [release-12.0.1] K8s: Dashboards: Mark as v1beta1 (#104422) 3 months ago
token.go K8s/Dashboards: Implement dashboards as StorageBackend (#90295) 1 year ago
types.go [release-12.0.1] K8s: Dashboards: Mark as v1beta1 (#104422) 3 months ago

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