From 7df263ff2eb6ac2e5d8cfcecd49b8bc4e65099de Mon Sep 17 00:00:00 2001 From: Timur Olzhabayev Date: Thu, 2 Feb 2023 11:10:29 +0100 Subject: [PATCH] Fixing plugin signing docs for the current latest version (#62755) * Fixing plugin signing docs for the current latest version * Deleting a file that should not have been there? --- docs/sources/developers/plugins/sign-a-plugin.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/developers/plugins/sign-a-plugin.md b/docs/sources/developers/plugins/sign-a-plugin.md index 6f611214160..ed626a7cdf9 100644 --- a/docs/sources/developers/plugins/sign-a-plugin.md +++ b/docs/sources/developers/plugins/sign-a-plugin.md @@ -32,7 +32,7 @@ To verify ownership of your plugin, you need to generate an API key that you'll Public plugins need to be reviewed by the Grafana team before you can sign them. -1. Submit your plugin for [review]({{< relref "publish-a-plugin/#publishing-your-plugin-for-the-first-time" >}}) +1. Submit your plugin for [review]({{< relref "package-a-plugin/#publishing-your-plugin-for-the-first-time" >}}) 2. When your plugin is approved, you're granted a plugin signature level. **Without a plugin signature level, you won't be able to sign your plugin**. 3. In your plugin directory, sign the plugin with the API key you just created. Grafana Sign Plugin creates a [MANIFEST.txt](#plugin-manifest) file in the `dist` directory of your plugin.