-
Notifications
You must be signed in to change notification settings - Fork 77
Version 2.0.2 being reported as unsigned #372
Comments
@albrechtflo-hg Thanks for letting me know! It was actually very helpful and I will mind that in the following release. |
@ofir5300 Yes, the release file worked for us, it is now running as expected. |
Hello, same problem here following the instructions here: https://grafana.com/grafana/plugins/doitintl-bigquery-datasource/ Grafana version: 7.4.5 Using the prior version worked fine. |
@Cristianasp |
Thank you @ofir5300 !! May I suggest you update the instructions at https://doitintl.github.io/bigquery-grafana/INSTALL ? |
Tnx @Cristianasp, Will do. |
Looks like there is a problem with the checksums in the MANIFEST.txt file in the 2.0.2.zip. I'm able to use the plugin when I set Grafana to allow unsigned plugins, but I would rather not do that. Here are the contents of the MANIFEST.txt file:
Here are the checksums of the files in the zip:
Note that the checksums don't match for several files. |
Are you guys going to update the |
Will create a new release soon. But please mind that it might be a long process.. |
Bug Report
The 2.0.2 version seems to be unsigned. I try to install it in Grafana Docker 8.1.4 using environment variable:
GF_INSTALL_PLUGINS=https://github.com/doitintl/bigquery-grafana/archive/2.0.2.zip;doit-bigquery-datasource
This is being reported as unsigned:
With 2.0.1, it is working fine.
Additional information: Using the Artifact Link from the "Releases" page, it is working fine (https://github.com/doitintl/bigquery-grafana/releases/download/2.0.2/doitintl-bigquery-datasource-2.0.2.zip). Seems to be an issue with the "archived" one.
Expected Behavior
The plugin is activated and displayed as signed.
Actual Behavior
The plugin is disabled and being reported as unsinged.
Steps to Reproduce the Problem
GF_INSTALL_PLUGINS
tohttps://github.com/doitintl/bigquery-grafana/archive/2.0.2.zip;doit-bigquery-datasource
Specifications
The text was updated successfully, but these errors were encountered: