From 5a3f0e869642d9273e50f1506329c1ae2aa49afa Mon Sep 17 00:00:00 2001 From: Timur Olzhabayev Date: Thu, 24 Nov 2022 19:00:33 +0100 Subject: [PATCH] Docs: Updating sign plugin docs (#59322) Updating sign plugin docs --- docs/sources/developers/plugins/sign-a-plugin.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/sources/developers/plugins/sign-a-plugin.md b/docs/sources/developers/plugins/sign-a-plugin.md index 4d5730a1d86..159136beca3 100644 --- a/docs/sources/developers/plugins/sign-a-plugin.md +++ b/docs/sources/developers/plugins/sign-a-plugin.md @@ -40,11 +40,9 @@ Public plugins need to be reviewed by the Grafana team before you can sign them. ```bash export GRAFANA_API_KEY= - npx @grafana/sign-plugin plugin:sign + npx @grafana/sign-plugin ``` -> **Note:** If running NPM 7+ the `npx` commands mentioned in this article may hang. The workaround is to use `npx --legacy-peer-deps `. - ## Sign a private plugin 1. 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. @@ -53,7 +51,7 @@ Public plugins need to be reviewed by the Grafana team before you can sign them. ```bash export GRAFANA_API_KEY= - npx @grafana/sign-plugin plugin:sign --rootUrls https://example.com/grafana + npx @grafana/sign-plugin --rootUrls https://example.com/grafana ``` ## Plugin signature levels