322 Commits (1b8e9b51b20adc3d37f3051f65a4bd5006bd1e5c)

Author	SHA1	Message	Date
Daniel Lee	94a54248c1	dashfolders: show folders use can save to in picker ... Instead of returning all folders a user has some sort of access to, this change creates a new end point that returns folders the user has write access to. This new endpoint is used in the folder picker	8 years ago
Daniel Lee	c27a74bb6b	dashfolders: check permissions for new dashboard ... ref #10275. Use the parent folder permissions if new dashboard and it does not have an id yet.	8 years ago
Daniel Lee	61ed0b0381	dashfolders: remove role requirements on dashboard routes ... and rely on the permission system instead.	8 years ago
Carl Bergquist	35106537f2	Replace Read Only Editor role with ViewersCanEdit setting (#10166) ... * removes readonly editor role * adds viewersCanEdit setting This enable you to allow viewers to edit/inspect dashboards in grafana in their own browser without allowing them to save dashboards * remove read only editor option from all dropdowns * migrates all read only viewers to viewers * docs: replace readOnlyEditor with viewersCanEdit	8 years ago
bergquist	ff1b71bc20	allow overriding dashboards from api	8 years ago
bergquist	5aab6b5c20	removes last pieces of dashboard.json	8 years ago
bergquist	f5eac2e91d	dashboards as cfg: expose dashboard service as interface	8 years ago
bergquist	16f072b320	dashboards as cfg: move saving logic for dashboards into its own service	8 years ago
bergquist	9cebb23e01	dashboards as cfg: revert minor changes	8 years ago
Daniel Lee	f70fb7dbf3	dashboard: fix home dashboard getting started panel	8 years ago
Torkel Ödegaard	df61558018	grid: fixed geting started panel pos	8 years ago
Torkel Ödegaard	4819e50441	newgrid: fixes to default home dashboard	8 years ago
Torkel Ödegaard	3066280216	added code from #8504, and #8021	8 years ago
Torkel Ödegaard	fc69d59cae	dashboard folder search fix	8 years ago
Daniel Lee	6d86afd472	dashfolders: use canadmin permission in settings menu	8 years ago
Torkel Ödegaard	aa634402d9	dashboard acl fixes	8 years ago
Torkel Ödegaard	74840178cf	refactoring dashboard folder security checks	8 years ago
Torkel Ödegaard	f7194878fe	dashboard guardian refactoring starting to work	8 years ago
Torkel Ödegaard	cbbbccf12a	refactoring dashoard folder guardian	8 years ago
Torkel Ödegaard	3fe031d25d	refactoring: Dashboard guardian	8 years ago
Torkel Ödegaard	d9dca72ee4	dashboard_folders: refactoring picker and folder selection in dashboard settings & save as menu	8 years ago
Daniel Lee	dd02bf7c9b	WIP: adds API check to stop folders being included in folders	8 years ago
Daniel Lee	92717ccafb	WIP: permission checking for dash version api methods	8 years ago
Daniel Lee	a861b1b9ba	WIP: check permissions for delete/post dashboard	8 years ago
Daniel Lee	3913f16550	WIP: add permission check for GetDashboard	8 years ago
Daniel Lee	5c89c4b2bd	WIP: dashlist in template for new folder	8 years ago
Daniel Lee	82afe8228f	WIP: add parentid to getdashboard query result	8 years ago
Daniel Lee	f1e1da39e3	WIP: get Dashboard Permissions ... The guardian class checks if the user is allowed to get the permissions for a dashboard.	8 years ago
Torkel Ödegaard	46412c8475	dasboard_history: security fix, added orgId filter to dashboard version lookup	8 years ago
Torkel Ödegaard	ef1dfed0d8	dasboard_history: big refactoring of how the compare api looked, now a POST with a model for new & base version, refactored a simplified UI code as well, this was done to lay foundation to make it possible to do diff against current in browser unsaved version	8 years ago
Torkel Ödegaard	948e5ae74d	dashboard_history: further css & markup fixes, removing style overrides & resuing existing styles and markup components	8 years ago
Torkel Ödegaard	7b5f7ed553	dashboard_history: SQL did not work when using MySQL, fixes to dashboard version numbering, so inserts start at 1, added migration to fix old dashboards with version 0	8 years ago
Torkel Ödegaard	e2061312f5	refactoring: moved compare dashboard version command out of sqlstore, the code in this command did not use any sql operations and was more high level, could be moved out and use existing queries to get the versions	8 years ago
Torkel Ödegaard	746d6cdc88	refactoring: changed name on compare command to make properties more explainatory	8 years ago
Torkel Ödegaard	cabbfe9adc	refactoring: moved dashboard history item formating (message) and fixed dashboard history migration issue, and removed from frontend tests that where no longer needed	8 years ago
Torkel Ödegaard	c87418d060	refactoring: Dashboard history restore operation is now reusing existing ... operations instead of duplicating a bunch of get & save logic.	8 years ago
Torkel Ödegaard	e18007153d	refactoring: Renamed dashboard version queries that wrongly had Command suffix, added missing OrgId to dashboard history commands and queries	8 years ago
sanchitraizada	77c046aac6	Implement review feedback	8 years ago
Ben Tranter	b6e46c9eb8	History and Version Control for Dashboard Updates ... A simple version control system for dashboards. Closes #1504. Goals 1. To create a new dashboard version every time a dashboard is saved. 2. To allow users to view all versions of a given dashboard. 3. To allow users to rollback to a previous version of a dashboard. 4. To allow users to compare two versions of a dashboard. Usage Navigate to a dashboard, and click the settings cog. From there, click the "Changelog" button to be brought to the Changelog view. In this view, a table containing each version of a dashboard can be seen. Each entry in the table represents a dashboard version. A selectable checkbox, the version number, date created, name of the user who created that version, and commit message is shown in the table, along with a button that allows a user to restore to a previous version of that dashboard. If a user wants to restore to a previous version of their dashboard, they can do so by clicking the previously mentioned button. If a user wants to compare two different versions of a dashboard, they can do so by clicking the checkbox of two different dashboard versions, then clicking the "Compare versions" button located below the dashboard. From there, the user is brought to a view showing a summary of the dashboard differences. Each summarized change contains a link that can be clicked to take the user a JSON diff highlighting the changes line by line. Overview of Changes Backend Changes - A `dashboard_version` table was created to store each dashboard version, along with a dashboard version model and structs to represent the queries and commands necessary for the dashboard version API methods. - API endpoints were created to support working with dashboard versions. - Methods were added to create, update, read, and destroy dashboard versions in the database. - Logic was added to compute the diff between two versions, and display it to the user. - The dashboard migration logic was updated to save a "Version 1" of each existing dashboard in the database. Frontend Changes - New views - Methods to pull JSON and HTML from endpoints New API Endpoints Each endpoint requires the authorization header to be sent in the format, ``` Authorization: Bearer <jwt> ``` where `<jwt>` is a JSON web token obtained from the Grafana admin panel. `GET "/api/dashboards/db/:dashboardId/versions?orderBy=<string>&limit=<int>&start=<int>"` Get all dashboard versions for the given dashboard ID. Accepts three URL parameters: - `orderBy` String to order the results by. Possible values are `version`, `created`, `created_by`, `message`. Default is `versions`. Ordering is always in descending order. - `limit` Maximum number of results to return - `start` Position in results to start from `GET "/api/dashboards/db/:dashboardId/versions/:id"` Get an individual dashboard version by ID, for the given dashboard ID. `POST "/api/dashboards/db/:dashboardId/restore"` Restore to the given dashboard version. Post body is of content-type `application/json`, and must contain. ```json { "dashboardId": <int>, "version": <int> } ``` `GET "/api/dashboards/db/:dashboardId/compare/:versionA...:versionB"` Compare two dashboard versions by ID for the given dashboard ID, returning a JSON delta formatted representation of the diff. The URL format follows what GitHub does. For example, visiting [/api/dashboards/db/18/compare/22...33](http://ec2-54-80-139-44.compute-1.amazonaws.com:3000/api/dashboards/db/18/compare/22...33) will return the diff between versions 22 and 33 for the dashboard ID 18. Dependencies Added - The Go package [gojsondiff](https://github.com/yudai/gojsondiff) was added and vendored.	8 years ago
Torkel Ödegaard	05772b30d7	feat(ux): completed work on getting started panel, #6466	9 years ago
Pavlos Daoglou	7f7f080ad8	[5443] Check if title is empty before save a new dashboard	9 years ago
bergquist	421c1eed82	fix(dashboard): fixes bug when saving dashboards	9 years ago
Carl Bergquist	df2b2e3058	feat(alerting): validate alerts before saving dashboard (#6691) ... ref #6576	9 years ago
bergquist	04f417a423	feat(alerting): enabled by default. configurable elert engine ... closes #6210	9 years ago
Torkel Ödegaard	b2acac3a41	feat(apps): more polish on app dashboard save warning, #5529	9 years ago
Torkel Ödegaard	68a8d9bc91	feat(apps): more work on plugin dashboard sync	9 years ago
Torkel Ödegaard	d44325affd	feat(apps): progress on app dashboard imports	9 years ago
Torkel Ödegaard	2b4a9954b1	feat(alerting): progress on alerting UI and model, refactoring of dashboard parser and tests into extractor component, moved tests from sqlstore to alerting package	9 years ago
Torkel Ödegaard	9741af2031	feat(logging): progress on new logging #4590	9 years ago
Torkel Ödegaard	22778e6efd	feat(logging): a lot of progress on moving to new logging lib, #4590	9 years ago