-
Notifications
You must be signed in to change notification settings - Fork 107
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
grafana_dashboard recource is not idempotent #47
Comments
Also, one can get
|
I fixed this in grafana 5.x by switching to dashboard provisioning instead of the puppet type that uses the API. http://docs.grafana.org/administration/provisioning/ In fact I had to switch from dashboard types to provisioning as I had all kinds of problems using the API including this one (dashboards titles not being found despite them being installed, resulting in errors, dashboards being continuously deployed as they are not idempotent ...). Switching to provisioning solved all my problems. May we should update the documentation for this alternative? |
I wonder how viable the solution to use the file provisioning is, because it makes it almost impossible to implement additional resources, e.g. resources for granting dashboard permissions to users and teams without requiring multiple puppet runs. Couldn't the provider be fixed to properly compare is/should? |
This should be resolved. When exporting a JSON file, you need to delete the "id", "uid" and "version" elements from that. The sanitized template should work. |
How to reproduce (e.g Puppet code you use)
What are you seeing
Karolis
The text was updated successfully, but these errors were encountered: