2014-12-22 19:25:08 +08:00
|
|
|
package sqlstore
|
|
|
|
|
|
|
|
|
|
import (
|
2015-02-04 18:35:59 +08:00
|
|
|
"bytes"
|
2015-02-05 18:10:56 +08:00
|
|
|
"fmt"
|
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.
2017-05-25 07:14:39 +08:00
|
|
|
"time"
|
2015-02-04 18:35:59 +08:00
|
|
|
|
2015-02-05 17:37:13 +08:00
|
|
|
"github.com/grafana/grafana/pkg/bus"
|
2015-03-23 03:14:00 +08:00
|
|
|
"github.com/grafana/grafana/pkg/metrics"
|
2015-02-05 17:37:13 +08:00
|
|
|
m "github.com/grafana/grafana/pkg/models"
|
2015-06-05 14:15:38 +08:00
|
|
|
"github.com/grafana/grafana/pkg/services/search"
|
2014-12-22 19:25:08 +08:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
func init() {
|
2014-12-29 20:58:06 +08:00
|
|
|
bus.AddHandler("sql", SaveDashboard)
|
|
|
|
|
bus.AddHandler("sql", GetDashboard)
|
2016-01-29 08:41:23 +08:00
|
|
|
bus.AddHandler("sql", GetDashboards)
|
2014-12-29 20:58:06 +08:00
|
|
|
bus.AddHandler("sql", DeleteDashboard)
|
|
|
|
|
bus.AddHandler("sql", SearchDashboards)
|
2015-01-07 01:39:26 +08:00
|
|
|
bus.AddHandler("sql", GetDashboardTags)
|
2016-03-17 16:01:58 +08:00
|
|
|
bus.AddHandler("sql", GetDashboardSlugById)
|
2016-07-08 15:35:06 +08:00
|
|
|
bus.AddHandler("sql", GetDashboardsByPluginId)
|
2014-12-22 19:25:08 +08:00
|
|
|
}
|
|
|
|
|
|
2014-12-29 20:58:06 +08:00
|
|
|
func SaveDashboard(cmd *m.SaveDashboardCommand) error {
|
2017-05-23 16:56:23 +08:00
|
|
|
return inTransaction(func(sess *DBSession) error {
|
2014-12-22 19:25:08 +08:00
|
|
|
dash := cmd.GetDashboardModel()
|
|
|
|
|
|
2015-01-06 00:04:29 +08:00
|
|
|
// try get existing dashboard
|
2015-05-04 14:19:29 +08:00
|
|
|
var existing, sameTitle m.Dashboard
|
2015-01-06 00:04:29 +08:00
|
|
|
|
2015-05-04 14:19:29 +08:00
|
|
|
if dash.Id > 0 {
|
|
|
|
|
dashWithIdExists, err := sess.Where("id=? AND org_id=?", dash.Id, dash.OrgId).Get(&existing)
|
|
|
|
|
if err != nil {
|
|
|
|
|
return err
|
|
|
|
|
}
|
|
|
|
|
if !dashWithIdExists {
|
|
|
|
|
return m.ErrDashboardNotFound
|
2015-03-03 05:24:01 +08:00
|
|
|
}
|
2015-05-04 14:19:29 +08:00
|
|
|
|
2015-03-03 05:24:01 +08:00
|
|
|
// check for is someone else has written in between
|
|
|
|
|
if dash.Version != existing.Version {
|
|
|
|
|
if cmd.Overwrite {
|
|
|
|
|
dash.Version = existing.Version
|
|
|
|
|
} else {
|
|
|
|
|
return m.ErrDashboardVersionMismatch
|
|
|
|
|
}
|
|
|
|
|
}
|
2016-07-08 19:41:46 +08:00
|
|
|
|
|
|
|
|
// do not allow plugin dashboard updates without overwrite flag
|
|
|
|
|
if existing.PluginId != "" && cmd.Overwrite == false {
|
|
|
|
|
return m.UpdatePluginDashboardError{PluginId: existing.PluginId}
|
|
|
|
|
}
|
2015-01-06 00:04:29 +08:00
|
|
|
}
|
|
|
|
|
|
2015-05-04 14:19:29 +08:00
|
|
|
sameTitleExists, err := sess.Where("org_id=? AND slug=?", dash.OrgId, dash.Slug).Get(&sameTitle)
|
|
|
|
|
if err != nil {
|
|
|
|
|
return err
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if sameTitleExists {
|
|
|
|
|
// another dashboard with same name
|
|
|
|
|
if dash.Id != sameTitle.Id {
|
|
|
|
|
if cmd.Overwrite {
|
|
|
|
|
dash.Id = sameTitle.Id
|
2017-06-06 20:39:57 +08:00
|
|
|
dash.Version = sameTitle.Version
|
2015-05-04 14:19:29 +08:00
|
|
|
} else {
|
|
|
|
|
return m.ErrDashboardWithSameNameExists
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
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.
2017-05-25 07:14:39 +08:00
|
|
|
parentVersion := dash.Version
|
|
|
|
|
affectedRows := int64(0)
|
2017-06-05 22:34:32 +08:00
|
|
|
|
2014-12-22 19:25:08 +08:00
|
|
|
if dash.Id == 0 {
|
2017-06-06 21:40:10 +08:00
|
|
|
dash.Version = 1
|
2017-09-06 17:23:52 +08:00
|
|
|
metrics.M_Api_Dashboard_Insert.Inc()
|
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.
2017-05-25 07:14:39 +08:00
|
|
|
dash.Data.Set("version", dash.Version)
|
2015-05-04 13:46:46 +08:00
|
|
|
affectedRows, err = sess.Insert(dash)
|
2014-12-22 19:25:08 +08:00
|
|
|
} else {
|
2017-06-05 22:34:32 +08:00
|
|
|
dash.Version += 1
|
2016-03-12 17:13:49 +08:00
|
|
|
dash.Data.Set("version", dash.Version)
|
2015-05-04 13:46:46 +08:00
|
|
|
affectedRows, err = sess.Id(dash.Id).Update(dash)
|
|
|
|
|
}
|
2017-06-05 22:34:32 +08:00
|
|
|
|
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.
2017-05-25 07:14:39 +08:00
|
|
|
if err != nil {
|
|
|
|
|
return err
|
|
|
|
|
}
|
2017-06-05 22:34:32 +08:00
|
|
|
|
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.
2017-05-25 07:14:39 +08:00
|
|
|
if affectedRows == 0 {
|
|
|
|
|
return m.ErrDashboardNotFound
|
|
|
|
|
}
|
2015-05-04 13:46:46 +08:00
|
|
|
|
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.
2017-05-25 07:14:39 +08:00
|
|
|
dashVersion := &m.DashboardVersion{
|
|
|
|
|
DashboardId: dash.Id,
|
|
|
|
|
ParentVersion: parentVersion,
|
2017-06-06 04:59:04 +08:00
|
|
|
RestoredFrom: cmd.RestoredFrom,
|
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.
2017-05-25 07:14:39 +08:00
|
|
|
Version: dash.Version,
|
|
|
|
|
Created: time.Now(),
|
|
|
|
|
CreatedBy: dash.UpdatedBy,
|
|
|
|
|
Message: cmd.Message,
|
|
|
|
|
Data: dash.Data,
|
|
|
|
|
}
|
2017-06-05 22:34:32 +08:00
|
|
|
|
|
|
|
|
// insert version entry
|
|
|
|
|
if affectedRows, err = sess.Insert(dashVersion); err != nil {
|
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.
2017-05-25 07:14:39 +08:00
|
|
|
return err
|
2017-06-05 22:34:32 +08:00
|
|
|
} else if affectedRows == 0 {
|
2015-05-04 13:46:46 +08:00
|
|
|
return m.ErrDashboardNotFound
|
2014-12-22 19:25:08 +08:00
|
|
|
}
|
|
|
|
|
|
2015-01-07 19:37:24 +08:00
|
|
|
// delete existing tabs
|
|
|
|
|
_, err = sess.Exec("DELETE FROM dashboard_tag WHERE dashboard_id=?", dash.Id)
|
|
|
|
|
if err != nil {
|
|
|
|
|
return err
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// insert new tags
|
|
|
|
|
tags := dash.GetTags()
|
|
|
|
|
if len(tags) > 0 {
|
|
|
|
|
for _, tag := range tags {
|
2015-01-20 21:15:48 +08:00
|
|
|
if _, err := sess.Insert(&DashboardTag{DashboardId: dash.Id, Term: tag}); err != nil {
|
|
|
|
|
return err
|
|
|
|
|
}
|
2015-01-07 19:37:24 +08:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2014-12-22 19:25:08 +08:00
|
|
|
cmd.Result = dash
|
|
|
|
|
|
|
|
|
|
return err
|
|
|
|
|
})
|
|
|
|
|
}
|
|
|
|
|
|
2014-12-29 20:58:06 +08:00
|
|
|
func GetDashboard(query *m.GetDashboardQuery) error {
|
2017-06-05 23:45:27 +08:00
|
|
|
dashboard := m.Dashboard{Slug: query.Slug, OrgId: query.OrgId, Id: query.Id}
|
2014-12-22 19:25:08 +08:00
|
|
|
has, err := x.Get(&dashboard)
|
2017-06-05 23:45:27 +08:00
|
|
|
|
2014-12-22 19:25:08 +08:00
|
|
|
if err != nil {
|
2014-12-29 20:58:06 +08:00
|
|
|
return err
|
2014-12-22 19:25:08 +08:00
|
|
|
} else if has == false {
|
2014-12-29 20:58:06 +08:00
|
|
|
return m.ErrDashboardNotFound
|
2014-12-22 19:25:08 +08:00
|
|
|
}
|
|
|
|
|
|
2016-03-12 17:13:49 +08:00
|
|
|
dashboard.Data.Set("id", dashboard.Id)
|
2014-12-29 20:58:06 +08:00
|
|
|
query.Result = &dashboard
|
|
|
|
|
return nil
|
2014-12-22 19:25:08 +08:00
|
|
|
}
|
|
|
|
|
|
2015-01-07 19:37:24 +08:00
|
|
|
type DashboardSearchProjection struct {
|
|
|
|
|
Id int64
|
|
|
|
|
Title string
|
|
|
|
|
Slug string
|
|
|
|
|
Term string
|
|
|
|
|
}
|
|
|
|
|
|
2015-05-13 19:36:13 +08:00
|
|
|
func SearchDashboards(query *search.FindPersistedDashboardsQuery) error {
|
2015-02-04 18:35:59 +08:00
|
|
|
var sql bytes.Buffer
|
|
|
|
|
params := make([]interface{}, 0)
|
|
|
|
|
|
|
|
|
|
sql.WriteString(`SELECT
|
|
|
|
|
dashboard.id,
|
|
|
|
|
dashboard.title,
|
|
|
|
|
dashboard.slug,
|
|
|
|
|
dashboard_tag.term
|
|
|
|
|
FROM dashboard
|
|
|
|
|
LEFT OUTER JOIN dashboard_tag on dashboard_tag.dashboard_id = dashboard.id`)
|
|
|
|
|
|
|
|
|
|
if query.IsStarred {
|
|
|
|
|
sql.WriteString(" INNER JOIN star on star.dashboard_id = dashboard.id")
|
|
|
|
|
}
|
|
|
|
|
|
2015-02-24 03:07:49 +08:00
|
|
|
sql.WriteString(` WHERE dashboard.org_id=?`)
|
2015-02-04 18:35:59 +08:00
|
|
|
|
2015-02-24 03:07:49 +08:00
|
|
|
params = append(params, query.OrgId)
|
2015-01-07 00:15:52 +08:00
|
|
|
|
2015-02-04 18:35:59 +08:00
|
|
|
if query.IsStarred {
|
|
|
|
|
sql.WriteString(` AND star.user_id=?`)
|
|
|
|
|
params = append(params, query.UserId)
|
|
|
|
|
}
|
|
|
|
|
|
2016-03-05 19:26:21 +08:00
|
|
|
if len(query.DashboardIds) > 0 {
|
|
|
|
|
sql.WriteString(" AND (")
|
|
|
|
|
for i, dashboardId := range query.DashboardIds {
|
|
|
|
|
if i != 0 {
|
2016-03-07 18:04:02 +08:00
|
|
|
sql.WriteString(" OR")
|
2016-03-05 19:26:21 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
sql.WriteString(" dashboard.id = ?")
|
|
|
|
|
params = append(params, dashboardId)
|
|
|
|
|
}
|
|
|
|
|
sql.WriteString(")")
|
|
|
|
|
}
|
|
|
|
|
|
2015-02-04 18:35:59 +08:00
|
|
|
if len(query.Title) > 0 {
|
2015-08-11 02:25:01 +08:00
|
|
|
sql.WriteString(" AND dashboard.title " + dialect.LikeStr() + " ?")
|
2015-02-04 18:35:59 +08:00
|
|
|
params = append(params, "%"+query.Title+"%")
|
|
|
|
|
}
|
2014-12-22 19:25:08 +08:00
|
|
|
|
2016-06-17 17:22:39 +08:00
|
|
|
sql.WriteString(fmt.Sprintf(" ORDER BY dashboard.title ASC LIMIT 1000"))
|
2015-02-05 18:10:56 +08:00
|
|
|
|
2015-01-07 19:37:24 +08:00
|
|
|
var res []DashboardSearchProjection
|
2016-03-07 18:04:02 +08:00
|
|
|
|
2015-02-04 18:35:59 +08:00
|
|
|
err := x.Sql(sql.String(), params...).Find(&res)
|
2015-01-07 19:37:24 +08:00
|
|
|
if err != nil {
|
|
|
|
|
return err
|
|
|
|
|
}
|
|
|
|
|
|
2015-05-13 19:36:13 +08:00
|
|
|
query.Result = make([]*search.Hit, 0)
|
|
|
|
|
hits := make(map[int64]*search.Hit)
|
2015-01-07 19:37:24 +08:00
|
|
|
|
|
|
|
|
for _, item := range res {
|
|
|
|
|
hit, exists := hits[item.Id]
|
|
|
|
|
if !exists {
|
2015-05-13 19:36:13 +08:00
|
|
|
hit = &search.Hit{
|
2015-02-03 00:17:57 +08:00
|
|
|
Id: item.Id,
|
2015-01-07 19:37:24 +08:00
|
|
|
Title: item.Title,
|
2015-05-12 20:11:30 +08:00
|
|
|
Uri: "db/" + item.Slug,
|
2015-05-13 19:36:13 +08:00
|
|
|
Type: search.DashHitDB,
|
2015-01-07 19:37:24 +08:00
|
|
|
Tags: []string{},
|
|
|
|
|
}
|
|
|
|
|
query.Result = append(query.Result, hit)
|
|
|
|
|
hits[item.Id] = hit
|
|
|
|
|
}
|
|
|
|
|
if len(item.Term) > 0 {
|
|
|
|
|
hit.Tags = append(hit.Tags, item.Term)
|
|
|
|
|
}
|
|
|
|
|
}
|
2014-12-22 19:25:08 +08:00
|
|
|
|
2014-12-29 20:58:06 +08:00
|
|
|
return err
|
2014-12-22 19:25:08 +08:00
|
|
|
}
|
|
|
|
|
|
2015-01-07 01:39:26 +08:00
|
|
|
func GetDashboardTags(query *m.GetDashboardTagsQuery) error {
|
2015-01-20 22:23:14 +08:00
|
|
|
sql := `SELECT
|
|
|
|
|
COUNT(*) as count,
|
|
|
|
|
term
|
|
|
|
|
FROM dashboard
|
|
|
|
|
INNER JOIN dashboard_tag on dashboard_tag.dashboard_id = dashboard.id
|
2015-02-24 03:07:49 +08:00
|
|
|
WHERE dashboard.org_id=?
|
2015-01-20 22:23:14 +08:00
|
|
|
GROUP BY term`
|
|
|
|
|
|
|
|
|
|
query.Result = make([]*m.DashboardTagCloudItem, 0)
|
2015-02-24 03:07:49 +08:00
|
|
|
sess := x.Sql(sql, query.OrgId)
|
2015-01-07 19:37:24 +08:00
|
|
|
err := sess.Find(&query.Result)
|
|
|
|
|
return err
|
2015-01-07 01:39:26 +08:00
|
|
|
}
|
|
|
|
|
|
2014-12-29 20:58:06 +08:00
|
|
|
func DeleteDashboard(cmd *m.DeleteDashboardCommand) error {
|
2017-05-23 16:56:23 +08:00
|
|
|
return inTransaction(func(sess *DBSession) error {
|
2015-08-12 15:23:46 +08:00
|
|
|
dashboard := m.Dashboard{Slug: cmd.Slug, OrgId: cmd.OrgId}
|
2016-04-25 17:22:13 +08:00
|
|
|
has, err := sess.Get(&dashboard)
|
2015-08-12 15:23:46 +08:00
|
|
|
if err != nil {
|
|
|
|
|
return err
|
|
|
|
|
} else if has == false {
|
|
|
|
|
return m.ErrDashboardNotFound
|
|
|
|
|
}
|
2014-12-22 19:25:08 +08:00
|
|
|
|
2015-08-12 15:23:46 +08:00
|
|
|
deletes := []string{
|
|
|
|
|
"DELETE FROM dashboard_tag WHERE dashboard_id = ? ",
|
|
|
|
|
"DELETE FROM star WHERE dashboard_id = ? ",
|
|
|
|
|
"DELETE FROM dashboard WHERE id = ?",
|
2016-11-06 17:49:43 +08:00
|
|
|
"DELETE FROM playlist_item WHERE type = 'dashboard_by_id' AND value = ?",
|
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.
2017-05-25 07:14:39 +08:00
|
|
|
"DELETE FROM dashboard_version WHERE dashboard_id = ?",
|
2017-10-07 16:31:39 +08:00
|
|
|
"DELETE FROM annotation WHERE dashboard_id = ?",
|
2015-08-12 15:23:46 +08:00
|
|
|
}
|
2014-12-22 19:25:08 +08:00
|
|
|
|
2015-08-12 15:23:46 +08:00
|
|
|
for _, sql := range deletes {
|
|
|
|
|
_, err := sess.Exec(sql, dashboard.Id)
|
|
|
|
|
if err != nil {
|
|
|
|
|
return err
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2017-05-23 16:56:23 +08:00
|
|
|
if err := DeleteAlertDefinition(dashboard.Id, sess); err != nil {
|
2016-04-26 21:48:29 +08:00
|
|
|
return nil
|
|
|
|
|
}
|
|
|
|
|
|
2015-08-12 15:23:46 +08:00
|
|
|
return nil
|
|
|
|
|
})
|
2014-12-22 19:25:08 +08:00
|
|
|
}
|
2016-01-29 08:41:23 +08:00
|
|
|
|
|
|
|
|
func GetDashboards(query *m.GetDashboardsQuery) error {
|
|
|
|
|
if len(query.DashboardIds) == 0 {
|
|
|
|
|
return m.ErrCommandValidationFailed
|
|
|
|
|
}
|
|
|
|
|
|
2016-06-23 22:30:12 +08:00
|
|
|
var dashboards = make([]*m.Dashboard, 0)
|
2016-01-29 08:41:23 +08:00
|
|
|
|
|
|
|
|
err := x.In("id", query.DashboardIds).Find(&dashboards)
|
2016-06-23 22:30:12 +08:00
|
|
|
query.Result = dashboards
|
2016-01-29 08:41:23 +08:00
|
|
|
|
|
|
|
|
if err != nil {
|
|
|
|
|
return err
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return nil
|
|
|
|
|
}
|
2016-03-17 16:01:58 +08:00
|
|
|
|
2016-07-08 15:35:06 +08:00
|
|
|
func GetDashboardsByPluginId(query *m.GetDashboardsByPluginIdQuery) error {
|
|
|
|
|
var dashboards = make([]*m.Dashboard, 0)
|
|
|
|
|
|
|
|
|
|
err := x.Where("org_id=? AND plugin_id=?", query.OrgId, query.PluginId).Find(&dashboards)
|
|
|
|
|
query.Result = dashboards
|
2016-01-29 08:41:23 +08:00
|
|
|
|
|
|
|
|
if err != nil {
|
|
|
|
|
return err
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return nil
|
|
|
|
|
}
|
2016-03-17 16:01:58 +08:00
|
|
|
|
2016-03-20 18:52:19 +08:00
|
|
|
type DashboardSlugDTO struct {
|
|
|
|
|
Slug string
|
|
|
|
|
}
|
|
|
|
|
|
2016-03-17 16:01:58 +08:00
|
|
|
func GetDashboardSlugById(query *m.GetDashboardSlugByIdQuery) error {
|
2016-03-20 18:52:19 +08:00
|
|
|
var rawSql = `SELECT slug from dashboard WHERE Id=?`
|
|
|
|
|
var slug = DashboardSlugDTO{}
|
|
|
|
|
|
|
|
|
|
exists, err := x.Sql(rawSql, query.Id).Get(&slug)
|
2016-03-17 16:01:58 +08:00
|
|
|
|
|
|
|
|
if err != nil {
|
|
|
|
|
return err
|
2016-03-20 18:52:19 +08:00
|
|
|
} else if exists == false {
|
2016-03-17 16:01:58 +08:00
|
|
|
return m.ErrDashboardNotFound
|
|
|
|
|
}
|
|
|
|
|
|
2016-03-20 18:52:19 +08:00
|
|
|
query.Result = slug.Slug
|
2016-03-17 16:01:58 +08:00
|
|
|
return nil
|
|
|
|
|
}
|