You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current repo is based on @grafana/toolkit which is deprecated now. Grafana announced the deprecation of the grafana/toolkit in v9.3 (November 2022) and has a new tool called create-plugin now available as a replacement. So, if the repo wants to develop new features then the migration should be provided.
Describe the solution you'd like
It would be nice to migrate to the new Grafana's create-plugin tool as it provides the following benefits:
More flexible: With create-plugin, you have more control over your plugins and its dependencies. The additional control translates into greater ease of customizing the tooling to fit your specific needs.
Faster development: With its out-of-the-box development environment, create-plugin can significantly reduce development time compared to using grafana-toolkit.
Improved testing capabilities: Easily test plugins with create-plugin GitHub workflows that automate unit and e2e test runs whenever you push changes to GitHub.
Technical support: The grafana-toolkit tool is deprecated and no longer supported by Grafana.
Better documentation: The documentation for create-plugin is more comprehensive and easier to discover than grafana-toolkit.
Describe alternatives you've considered
I don't think there are any alternatives.
Which sides should be considered to develop?
[v] Frontend(React)
[v] Backend(Golang)
The create-plugin tool creates a lot of new things, such as configs for the frontend part or docker-compose.yaml that has the Grafana instance inside. So, the changes are related to both parts, and also infrastructure additions will be provided.
Is your feature request related to a problem? Please describe.
The current repo is based on
@grafana/toolkit
which is deprecated now. Grafana announced the deprecation of thegrafana/toolkit
in v9.3 (November 2022) and has a new tool called create-plugin now available as a replacement. So, if the repo wants to develop new features then the migration should be provided.Describe the solution you'd like
It would be nice to migrate to the new Grafana's
create-plugin
tool as it provides the following benefits:The migrations guide is posted on - https://grafana.com/developers/plugin-tools/migration-guides/migrate-from-toolkit
Describe alternatives you've considered
I don't think there are any alternatives.
Which sides should be considered to develop?
The
create-plugin
tool creates a lot of new things, such as configs for the frontend part ordocker-compose.yaml
that has the Grafana instance inside. So, the changes are related to both parts, and also infrastructure additions will be provided.Additional context
Overview on how to create a new plugin - https://grafana.com/developers/plugin-tools/
Migration guide - https://grafana.com/developers/plugin-tools/migration-guides/migrate-from-toolkit
The text was updated successfully, but these errors were encountered: