add taosdata-tdengine-datasource plugin.

[sangshuduo]

For verifying the TDengine data source plugin, please refer to https://www.taosdata.com/en/documentation/connections-with-other-tools/#Grafana. But need change TDengine RESTful port from 6020 to 6041.

TDengine docker can be run as following command:

docker run tdengine/tdengine:latest

Thanks.

[marcusolsson]

Hi @sangshuduo, and thank you for considering contributing your plugin!

I found a few issues when I validated your plugin. Please take a look, and fix all errors (warnings are ok).

Validate your plugin

[sangshuduo]

@marcusolsson thanks for your review. I checked the validation result and fixed most of them. But I can't find how to claim my organization after login with my github account. Could you please point me where I can claim? Thanks.

[marcusolsson]

@sangshuduo Your username on Grafana.com must be the same as the first part of the plugin ID. If you logged in with GitHub, I believe your Grafana.com will be the same as your GitHub username, which is sangshuduo. The plugin however says it belongs to taosdata.

You can change your username to taosdata from the settings in your grafana.com account.

[sangshuduo]

OK. I already changed my username to taosdata. Please let me know if anything I missed. Thanks.

[sangshuduo]

will resubmit PR since process changed.

[sangshuduo]

Hi Marcus, I followed the new process and signed my plugin and resubmitted PR [1]. Please let me know if something needs to be revised or fixed. Thanks, Shuduo [1]: #812

…

On Wed, Nov 18, 2020 at 10:53 PM Marcus Olsson ***@***.***> wrote: Thank you for your patience while waiting for us to review your plugin. We're working hard at improving the plugin experience for both users and authors. I'd like to share some important information on how to package and publish plugins going forward. Since Grafana 7.3, we require all plugins to be *signed*. By signing your plugin, users can guarantee the integrity of the plugin and that the plugin version they've installed hasn't been modified since it was released. For more information on how to sign your plugin, refer to Sign a plugin <https://grafana.com/docs/grafana/latest/developers/plugins/sign-a-plugin/> . With this, we now require plugins to be *packaged* before we publish them. This means that instead of a commit containing a dist directory, you will need to submit a link to a ZIP archive containing your plugin. For more information on how to package your plugin, refer to Package a plugin <https://grafana.com/docs/grafana/latest/developers/plugins/package-a-plugin/> . Once you've packaged your plugin, you'll need to update your entry to repo.json to the new format. You can read more on how to do this under Add a plugin to repo.json <https://github.com/grafana/grafana-plugin-repository#add-a-plugin-to-repojson> . To summarize, to publish your plugin, make sure that you: 1. Sign your plugin <https://grafana.com/docs/grafana/latest/developers/plugins/sign-a-plugin/> 2. Package your plugin <https://grafana.com/docs/grafana/latest/developers/plugins/package-a-plugin/> 3. Create a new GitHub release and upload the packaged plugin as a release asset 4. Update your repo.json entry <https://github.com/grafana/grafana-plugin-repository#add-a-plugin-to-repojson> Here's an example <https://github.com/marcusolsson/grafana-jsonapi-datasource/releases/tag/v0.6.0> of a properly packaged plugin. In the same repository, you can find a GitHub Action <https://github.com/marcusolsson/grafana-jsonapi-datasource/blob/master/.github/workflows/main.yml> that signs, packages, and releases the plugin whenever you create a new tag. Once you've created a GitHub release with the packaged plugin, you can right-click the release asset, copy the link, and validate it using the plugin validator <https://grafana-plugins-web-vgmmyppaka-lz.a.run.app>. Finally, in the November community call <https://groups.google.com/g/grafana-developers/c/ps2vzCXRDCM/m/i7uAK1u9AQAJ>, I'll be walking through the steps needed to sign and package your plugin. A recording will be made available on our YouTube account <https://www.youtube.com/playlist?list=PLDGkOdUX1Ujo0OyE5HFffHE9GJVvaVXGs>, in case you can't make it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#704 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGJTAIPSW4XY5DJPAUSCHDSQPNXPANCNFSM4P7GQIHQ> .