It should be possible that dashboards which cotnains a specific tag, are pushed into a configured Git repository.

• The tag should be kept according to the configuration used.
• The folder structure should be kept as well.

This task should be triggerd as soon as the datasource configuration is updated and the push task has been enabled.

It should be possible that dashboards are pulled from a configured Git repository and inserted into Grafana the specified Grafana instance.

• Dashboards should only be imported when they have been modified since the last import.

This task should be triggerd as soon as the datasource configuration is updated and the pull task has been enabled.

In order to properly configure the datasource, the configuration UI has to be finalized.

The following properties should be able to configure:

• grafanaUrl - The URL to reach the API of the current Grafana instance
• grafanaApiToken - An API token for the current Grafana instance
• gitUrl - The SSH URL for the Git repository to use
• privateSshKey - The private key which should be used to interact with the specified Git repository

The following properties should be configurable in the scope of pushing and pulling dashboards. They should be nested withing the properties pullConfiguration and pullConfiguration:

• enable - Whether the task is enabled or not
• gitBranch - The branch name to use
• syncInterval - The interval when the task should be triggered
• filter - The filter to use for selecting specific dashboard. (Whitelist)

The push configuration has the following additonal configuration property:

• tagPattern: The pattern of tags used to determine whether a dashboard should be pushed to the Git repository
• pushTags: Whether the "selector tag" should be removed when pushed

Due to the fact that this is a datasource plugin, users are able to use it in their panels. When the plugin is used in a panel, it should display a note that it cannot be used as a normal datasource

This pr:

• Updates go-git and go-billy to v5
• Adds support for gitlab token (should also work with github but haven't tested that)

I first thought I would have to use http.TokenAuth but this except was present in go-git:

// IMPORTANT: If you are looking to use OAuth tokens with popular servers (e.g.
// GitHub, Bitbucket, GitLab) you should use BasicAuth instead. These servers
// use basic HTTP authentication, with the OAuth token as user or password.
// Check the documentation of your git server for details.

Currently, it is neccessary that an API URL and API token have to be created and configured for the current Grafana instance. It would be good when users does not need this. Instead the plugin should be able to access dashboard information without the need of configuring an API token and the API URL.

Instead of considering all dashboards in the synchronization proces (according to the sync-tag), it should be able to specify a whitelist-filter. Only dashboard matching this filter, should be considered in the sync process.

• It should be able to use the whitelist filter for folders or dashboards

Instead of triggering the push and pull logic when updating the datasource configuration, it should be triggered in a specific interval, e.g. 1 minute.

It would be better when cron-expressions could be used instead of a fixed interval (e.g. 5 4 * * * to sync each day at 04:05).