![]() ![]() They may not be distributed to the Grafana community, and are not published in the Grafana catalog. Private Plugins are for use on your own Grafana. You can create and sign a Private Plugin for any technology at no charge. You can sign your plugin under three different signature levels. The signature level of your plugin determines how you can distribute it. To sign a plugin, you need to decide the signature level you want to sign it under. The rootUrls flag accepts a comma-separated list of URLs to the Grafana instances where you intend to install the plugin. Grafana Sign Plugin creates a MANIFEST.txt file in the dist directory of your plugin. In your plugin directory, sign the plugin with the API key you just created. Without a plugin signature level, you won’t be able to sign your plugin. When your plugin is approved, you’re granted a plugin signature level. Public plugins need to be reviewed by the Grafana team before you can sign them. For example, if your account slug is acmecorp, you need to prefix the plugin ID with acmecorp-.Ĭreate a Grafana Cloud API key with the PluginPublisher role. You can find the plugin ID in the plugin.json file inside your plugin directory. ![]() Make sure that the first part of the plugin ID matches the slug of your Grafana Cloud account. To verify ownership of your plugin, you need to generate an API key that you’ll use every time you need to sign a new version of your plugin. If you intend to only use the plugin within your organization, you can sign it under a private signature level. Public plugins are available from /plugins and can be installed by anyone. If you want to make your plugin publicly available outside of your organization, you need to sign your plugin under a community or commercial signature level. Important: Future versions of Grafana will require all plugins to be signed.īefore you can sign your plugin, you need to decide whether you want to sign it as a public or a private plugin. All Grafana Labs-authored backend plugins, including Enterprise plugins, are signed. This gives users a way to make sure plugins haven’t been tampered with. Signing a plugin allows Grafana to verify the authenticity of the plugin with signature verification. ![]()
0 Comments
Leave a Reply. |