refactor: move the migration guide to /Developers

This commit is contained in:
Levente Balogh 2023-04-11 13:55:02 +02:00
parent 7065b04bf6
commit 8f31af8dfd
8 changed files with 9 additions and 7 deletions

View File

@ -12,6 +12,7 @@ title: Migration guides
<script>
(function () {
// Previously all the migration docs were on a single page, and the different sections could be linked using URL hashes.
var anchorRedirects = {
"migrate-a-plugin-from-angular-to-react": "./angular-react/",
"from-version-62x-to-74x": "./v6.x-v7.x/",
@ -25,9 +26,10 @@ title: Migration guides
"from-version-91x-to-92x": "./v9.1.x-v9.2.x/",
"from-version-93x-to-94x": "./v9.3.x-v9.4.x/",
};
var anchor = window.location.hash.substring(1);
if (anchor) {
window.location.replace(anchorRedirects[anchor]);
var hash = window.location.hash.substring(1);
var redirectTo = anchorRedirects[hash];
if (redirectTo) {
window.location.replace(redirectTo);
}
})();
</script>

View File

@ -74,7 +74,7 @@ async query(options: DataQueryRequest<MyQuery>): Promise<DataQueryResponse> {
## Troubleshoot plugin migration
As of Grafana 7.0, backend plugins can now be cryptographically signed to verify their origin. By default, Grafana ignores unsigned plugins. For more information, refer to [Allow unsigned plugins]({{< relref "../../../../administration/plugin-management/#allow-unsigned-plugins" >}}).
As of Grafana 7.0, backend plugins can now be cryptographically signed to verify their origin. By default, Grafana ignores unsigned plugins. For more information, refer to [Allow unsigned plugins]({{< relref "../../../administration/plugin-management/#allow-unsigned-plugins" >}}).
## From version 6.5.x to 7.3.0

View File

@ -154,7 +154,7 @@ We strongly recommend that you not allow unsigned plugins in your Grafana instal
To sign your plugin, see [Sign a plugin](https://grafana.com/docs/grafana/latest/developers/plugins/sign-a-plugin/#sign-a-plugin).
You can still run and develop an unsigned plugin by running your Grafana instance in [development mode](https://grafana.com/docs/grafana/latest/administration/configuration/#app_mode). Alternatively, you can use the [allow_loading_unsigned_plugins]({{< relref "../../../../setup-grafana/configure-grafana/#allow_loading_unsigned_plugins" >}}) configuration setting.
You can still run and develop an unsigned plugin by running your Grafana instance in [development mode](https://grafana.com/docs/grafana/latest/administration/configuration/#app_mode). Alternatively, you can use the [allow_loading_unsigned_plugins]({{< relref "../../../setup-grafana/configure-grafana/#allow_loading_unsigned_plugins" >}}) configuration setting.
## Update react-hook-form from v6 to v7
@ -196,7 +196,7 @@ import { cx, css } from '@emotion/css';
## Update needed for app plugins using dashboards
To make side navigation work properly - app plugins targeting Grafana `8.+` and integrating into the side menu via [addToNav]({{< relref "../../metadata/#properties-4" >}}) property need to adjust their `plugin.json` and all dashboard json files to have a matching `uid`.
To make side navigation work properly - app plugins targeting Grafana `8.+` and integrating into the side menu via [addToNav]({{< relref "../../plugins/metadata/#properties-4" >}}) property need to adjust their `plugin.json` and all dashboard json files to have a matching `uid`.
**`plugin.json`**

View File

@ -69,7 +69,7 @@ We have removed the deprecated `getFormStyles` function from [grafana-ui](https:
### /api/ds/query replaces /api/tsdb/query
We have removed the deprecated `/api/tsdb/query` metrics endpoint. Use [/api/ds/query]({{< relref "../../../http_api/data_source/#query-a-data-source" >}}) instead
We have removed the deprecated `/api/tsdb/query` metrics endpoint. Use [/api/ds/query]({{< relref "../../http_api/data_source/#query-a-data-source" >}}) instead
### selectOptionInTest has been removed