Skip to content

Allow installation of plugins from arbitrary URLs #1572

Closed
@siegenthalerroger

Description

@siegenthalerroger

Is your feature request related to a problem? Please describe.
I want to install the "explore-logs" experimental Grafana plugin. This isn't available on Grafana's "store" and must be loaded from a provided URL. This isn't possible as the Datasource and Dashboard CRs don't expose a URL field for the plugins. Further it isn't possible to set the GF_INSTALL_PLUGINS env variable manually, as the operator overrides this.

(If applicable)If your feature request solves a bug please provide a link to the community issue
#1393 (comment)

Describe the solution you'd like
A few variants of solutions I'd consider functional:

  • Extend the Dashboard and Datasource CRDs to allow a URL to also be defined for plugins
  • Extend the Grafana CRD to allow the definition of plugins with URLs (more secure as doesn't allow arbitrary URLs from decentral sources)
  • Allow the definition of the GF_INSTALL_PLUGINS env variable in the Grafana CRD and merge the result instead of overriding it.

Describe alternatives you've considered / Additional context
I'm not sure how this would interop with the "app" plugins problems with enablement (doesn't seem to effect the explore-logs plugin despite this being described as an "app") - #1392

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestneeds triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions