apitech
/
grafana
mirror of https://github.com/grafana/grafana
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
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.
53805 Commits
2179 Branches
608 Tags
1.9 GiB
 
 
 
 
 
 
Tag: Branch: Tree: db97da3465
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'db97da3465'
${ noResults }
grafana/pkg/registry/apis/dashboard/legacy
History
Ryan McKinley 5a30e12a10
SQLTemplate: Make Ident only work for identifiers (not any string) (#92387) 		10 months ago
..
testdata SQLTemplate: Make Ident only work for identifiers (not any string) (#92387) 10 months ago
README.md K8s/Dashboards: Implement dashboards as StorageBackend (#90295) 12 months ago
queries.go LibraryPanels: Expose library panels in dashboard apiserver (#92213) 10 months ago
queries_test.go SQLTemplate: Make Ident only work for identifiers (not any string) (#92387) 10 months ago
query_dashboards.sql SQL: Add more legacy helpers (#92006) 10 months ago
query_panels.sql LibraryPanels: Expose library panels in dashboard apiserver (#92213) 10 months ago
sql_dashboards.go LibraryPanels: Expose library panels in dashboard apiserver (#92213) 10 months ago
storage.go SQL: Add more legacy helpers (#92006) 10 months ago
token.go K8s/Dashboards: Implement dashboards as StorageBackend (#90295) 12 months ago
types.go LibraryPanels: Expose library panels in dashboard apiserver (#92213) 10 months ago
utils.go K8s/Dashboards: Implement dashboards as StorageBackend (#90295) 12 months ago
utils_test.go K8s/Dashboards: Implement dashboards as StorageBackend (#90295) 12 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