577 Commits (d95eabfeec00a2386a64db9461e119ff0c8ac4f6)

Author	SHA1	Message	Date
Torkel Ödegaard	b494fd7689	dashboard folders acl work	9 years ago
Torkel Ödegaard	cbbbccf12a	refactoring dashoard folder guardian	9 years ago
Torkel Ödegaard	3fe031d25d	refactoring: Dashboard guardian	9 years ago
Daniel Lee	dd02bf7c9b	WIP: adds API check to stop folders being included in folders	9 years ago
Daniel Lee	699f9095e2	WIP: remove permissions when deleting global user	9 years ago
Daniel Lee	9f79b9b8c5	WIP: fix go fmt error	9 years ago
Daniel Lee	9eccb4e79f	WIP: API - add dash permission	9 years ago
Daniel Lee	2097ed0bb8	WIP: Permission Type as string in permission query	9 years ago
Daniel Lee	5c89c4b2bd	WIP: dashlist in template for new folder	9 years ago
Daniel Lee	fff7b706d6	WIP: user group additions	9 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.	9 years ago
Daniel Lee	13314f23ba	WIP: Can remove dashboard permission - sql	9 years ago
Daniel Lee	97c13b77bf	WIP: Add or update Dashboard ACL ... SQL Integration Tests for the guardian class too.	9 years ago
Daniel Lee	3785894b40	WIP: guardian service for search ... Removes restricted dashboards from search result.	9 years ago
Daniel Lee	552935031b	WIP: API methods for add/remove members to user group	9 years ago
Daniel Lee	0a1df0905e	WIP: add update user group command	9 years ago
Daniel Lee	233cd7af4a	WIP: add user group search	9 years ago
Daniel Lee	af67aea2a9	WIP: add usergroup commands and queries	9 years ago
Daniel Lee	1248728d7f	WIP: rough prototype of dashboard folders ... Breaks some stuff like selected dash in the search result. In dashboard search, if the user is not searching then the result is returned as a tree structure. No ACL's or user group ux yet.	9 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	9 years ago
Torkel Ödegaard	746d6cdc88	refactoring: changed name on compare command to make properties more explainatory	9 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	9 years ago
Torkel Ödegaard	c87418d060	refactoring: Dashboard history restore operation is now reusing existing ... operations instead of duplicating a bunch of get & save logic.	9 years ago
Torkel Ödegaard	e18007153d	refactoring: Renamed dashboard version queries that wrongly had Command suffix, added missing OrgId to dashboard history commands and queries	9 years ago
sanchitraizada	77c046aac6	Implement review feedback	9 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.	9 years ago
Torkel Ödegaard	c34db77f04	grafana_com: changed name of oauth grafana_net integration (old settings names still work), and updated login button look, closes #8415	9 years ago
Torkel Ödegaard	4ce0bf4d16	mysql: improved mysql data source, added test feature when adding data source, fixed cache issue	9 years ago
Torkel Ödegaard	368e847d12	feat: added api health endpoint that does not require auth and never creates sessions, returns db status as well. #3302	9 years ago
Torkel Ödegaard	87c978ebc9	fix: better error handling / messsage when testing email notification when stmp is not configured, fixes #8093	9 years ago
Dan Cech	b489e93d94	Config Array Syntax (#8204) ... * refactor util encryption library so it doesn't have to import log * add util.SplitString to handle space and/or comma-separated config lines * go fmt	9 years ago
Dan Cech	f490c5f12c	use X-Grafana-Org-Id header to ensure backend uses correct org (#8122)	9 years ago
Torkel Ödegaard	1cd632cc43	plugins: added state property to plugins	9 years ago
Torkel Ödegaard	d6d2080f11	mysql: minor progress on response processing	9 years ago
Torkel Ödegaard	bd4f073425	mysql: minor update	9 years ago
Torkel Ödegaard	998f04e1e8	mysql: testdata	9 years ago
bergquist	00dddca26a	alerting: dedupe alert notifications when running multiple servers ... alert notifications will only be sent if the database value is updated. ref #6957	9 years ago
bergquist	52566376b2	tech(server): remove unused code	9 years ago
Daniel Lee	193d468ed3	admin: adds paging to global user list ... Currently there is a limit of 1000 users in the global user list. This change introduces paging so that an admin can see all users and not just the first 1000. Adds a new route to the api - /api/users/search that returns a list of users and a total count. It takes two parameters perpage and page that enable paging. Fixes #7469	9 years ago
huydx	143cbe921f	(feat) support datasource delete by name api	9 years ago
Daniel Lee	1294b203e6	admin: adds paging to global user list ... Currently there is a limit of 1000 users in the global user list. This change introduces paging so that an admin can see all users and not just the first 1000. Adds a new route to the api - /api/users/search that returns a list of users and a total count. It takes two parameters perpage and page that enable paging. Fixes #7469	9 years ago
Torkel Ödegaard	fce2e341d2	mergefix(): fixed issue with master merge	9 years ago
huydx	376d2d56bf	(feature) add LINE notify to notifier	9 years ago
bergquist	9a3e51894b	tech(alerting): remove unused property	9 years ago
Torkel Ödegaard	8bccbdafd2	feat(live): minor progress on stream manager	9 years ago
bergquist	6c2c3c7e24	Revert "fix(alerting): pause dto can only pause one" ... This reverts commit b2c5a6a037.	10 years ago
bergquist	b2c5a6a037	fix(alerting): pause dto can only pause one	10 years ago
bergquist	ecdf1888c4	feat(alerting): removes pause per datasource	10 years ago
bergquist	fb6aa0e026	feat(api): adds endpoint for mass pausing alerts ... ref #6589	10 years ago
bergquist	c467e48940	feat(notifications): removes html escaping subject ... closes #6905	10 years ago