From c0875d5a61835c135d75cfd952d25788f0e63c39 Mon Sep 17 00:00:00 2001 From: "Grot (@grafanabot)" <43478413+grafanabot@users.noreply.github.com> Date: Fri, 29 Oct 2021 13:42:28 -0600 Subject: [PATCH] Added note. (#41118) (#41121) (cherry picked from commit 161d92e12fc5624d91e955740eaf4fc01359a65f) Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com> --- docs/sources/plugins/plugin-signatures.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/sources/plugins/plugin-signatures.md b/docs/sources/plugins/plugin-signatures.md index b0c81e5df59..c20ee236692 100644 --- a/docs/sources/plugins/plugin-signatures.md +++ b/docs/sources/plugins/plugin-signatures.md @@ -38,7 +38,9 @@ All plugins is signed under a _signature level_. The signature level determines ## Allow unsigned plugins -We strongly recommend that you don't run unsigned plugins in your Grafana installation. If you're aware of the risks and you still want to load an unsigned plugin, refer to [Configuration]({{< relref "../administration/configuration.md#allow_loading_unsigned_plugins" >}}). +> **Note:** Unsigned plugins are not supported in Grafana Cloud. + +We strongly recommend that you don't run unsigned plugins in your Grafana instance. If you're aware of the risks and you still want to load an unsigned plugin, refer to [Configuration]({{< relref "../administration/configuration.md#allow_loading_unsigned_plugins" >}}). If you've allowed loading of an unsigned plugin, then Grafana writes a warning message to the server log: