Is your feature request related to a problem? Please describe.
When configuring additional options into the Grafana plugin, ex: SMTP; the configuration can be done via environment variables but it is currently not allowed withing Thinger.io Platform.
Also, it could be possible to use Node-RED projects by passing an environment variable (NODE_RED_ENABLE_PROJECTS)
Describe the solution you'd like
There should be a way to pass user defined environment variables into the context of the plugin, this way some configurations can be persisted within Thinger and not affected by a plugin upgrade.
In a way this would extend the plugin.json of the plugin.
Describe alternatives you've considered
An alternative is to deploy the plugin locally, carrying the responsibility of the updates and alignment of version to the end-user.
Is your feature request related to a problem? Please describe. When configuring additional options into the Grafana plugin, ex: SMTP; the configuration can be done via environment variables but it is currently not allowed withing Thinger.io Platform. Also, it could be possible to use Node-RED projects by passing an environment variable (NODE_RED_ENABLE_PROJECTS)
Describe the solution you'd like There should be a way to pass user defined environment variables into the context of the plugin, this way some configurations can be persisted within Thinger and not affected by a plugin upgrade. In a way this would extend the plugin.json of the plugin.
Describe alternatives you've considered An alternative is to deploy the plugin locally, carrying the responsibility of the updates and alignment of version to the end-user.