plugin-tools
plugin-tools copied to clipboard
grafana
Create Grafana plugins with ease.
This is just an idea and not verified whether it actually works or not, especially substituting the version within the levitate call. Its very brittle based on how people _could_...
### Which areas does this feature request relate to - [ ] Create Plugin - [ ] Sign Plugin - [X] Plugin E2E - [ ] Documentation The purpose of...
**What this PR does / why we need it**: Currently the GitHub workflow files are only generated during the `generate` command. Running `update` doesn't do anything with workflows and for...
Should list npm, pnpm and yarn - [ ] package a plugin only references yarn currently - [ ] sign a plugin only references npx Can use `getting-started` as an...
Reading this blog post: https://aws.amazon.com/blogs/mt/extend-your-amazon-managed-grafana-experience-with-grafana-community-plugins/ noticing the paragraph on security, noticing that there are a few things we could say about security in our docs that we don't, and it...
This page is lacking detail and probably needs revisiting to ensure we are providing appropriate guidance. Questions / considerations: - The opening statement claims app plugins can nest datasources and...
### Which areas does this feature request relate to - [ ] Create Plugin - [ ] Sign Plugin - [x] Plugin E2E - [ ] Documentation ### Problem This...
### Which package(s) does this bug affect? - [X] Create Plugin - [ ] Sign Plugin - [ ] Plugin E2E ### Package versions ```shell @grafana/[email protected] ``` ### What happened?...
https://grafana.com/developers/plugin-tools/publish-a-plugin/publish-a-plugin Should be updated to include that you need to be an admin for the Grafana Cloud organization being used to publish a plugin.
To help users correctly sign a private plugin we should provide ~2 examples in the [docs](https://grafana.com/developers/plugin-tools/publish-a-plugin/sign-a-plugin#sign-a-private-plugin) Should include: - [ ] comma separated list - [ ] localhost - [...