-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Operator does not correctly import dashboards with variables #1303
Comments
Same issue here with Grafana-Operator v5.4.1 and Grafana v10.1.4. |
@bheading isn't |
@pb82 But if so, how can we overwrite template variables in Grafana dashboards with the operator? |
Its possible to use grafanadashboard.spec.datasources to map a value to a constant defined in __inputs Not sure if this if is an officially recommended approach though, it would be preferable not to have to reference a field named datasourceName.
|
I currently don't have time to take a deeper look, at this. |
This issue hasn't been updated for a while, marking as stale, please respond within the next 7 days to remove this label |
/remove-lifecycle stale |
This issue hasn't been updated for a while, marking as stale, please respond within the next 7 days to remove this label |
*Description
The Operator does not correctly set up a variable defined in the
__inputs
section of a dashboardVersion
v5.4.2
To Reproduce
Steps to reproduce the behavior:
Set up a Grafana instance on kind in the usual way.
use
kubectl apply -f
to apply the attached dashboard : test-dashboard.yaml.gzLog into Grafana and notice that the panel shows
${VAR_TESTCONSTANT}
instead of the expected valueexample-constant
.Expected behavior
When Grafana is importing the dashboard it should inflate the variables within the
__inputs
section.Screenshots
Expected outcome :
Observed outcome :
Runtime (please complete the following information):
The text was updated successfully, but these errors were encountered: