Plugin.json update #138
Unanswered
ddramireddy
asked this question in
Q&A
Replies: 2 comments
-
The error you're getting is because you're modifying a signed version of the plugin. If you remove the MANIFEST.txt file, you'll get rid of the warning. Though the plugin won't be signed so you'd have to allow it in your grafana.ini. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @ddramireddy would you be able to share your patch of the plugin that implements this? I'm interested in doing something similar. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @marcusolsson,
I am planning to use your plugin to call our REST API. Our API works based on JWT token. Initially, we need to call Signin API to get the JWT Token and use that token to call the other API. This token needs to be renewed for every 30 mins.
As per following link, I updated plugin.json and added the routes. However, On restarting grafana, I am getting the error "Failed to start plugin. Plugin file's signature has been modified versus manifest". Is it not allowed to update "plugin.json"? If so, what is the alternative to add tokenAuth section?
https://www.bookstack.cn/read/grafana-v6.2/99ade7a5e84896a8.md
Beta Was this translation helpful? Give feedback.
All reactions