With the latest versions of Grafana, plugins have to be signed otherwise they won't work
raulmarinperez opened this issue · comments
I've followed the very well documented tutorial, but I was unable to make it the plugin work up until I signed it with a private signature following the steps here: https://grafana.com/docs/grafana/latest/developers/plugins/sign-a-plugin/
It would be nice to add these additional steps in the documentation to make it clearer for people new to this topic.
For exclusive local development I found an update to the grafana config effective:
[plugins]
# Enter a comma-separated list of plugin identifiers to identify plugins to load even if they are unsigned. Plugins with modified signatures are never loaded.
allow_loading_unsigned_plugins = <your-plugin-name>
This allowed me to move the plugin forward and worry about the signing when I got ready to deploy. Especially with the intent being that one can call the npx generator and have a functioning templated plugin, this is a big tripping hazard.