-
Notifications
You must be signed in to change notification settings - Fork 405
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
Check remote changes #1213
Check remote changes #1213
Conversation
ff66a60
to
5753b09
Compare
5753b09
to
1f71b29
Compare
LGTM! We just need go-lint to be happy again |
So I took the freedom to fix the linting. |
@olejeglejeg could you take a look at this PR. Jsonnet should generate standard grafana json I assume. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed offline, it would be nice to do the same for datasources.
Also, it wouldn't hurt to add a small unit test for this.
Yes, it's true, since the json generation made above, it mustn't cause issues with this part. But I have small opinion that want to clarify: I thought that behaviour of the operator does not permit any changes with dashboards except from the code and it was a requirement and target. Is it so? This PR is changing it which can force clients to mark their dashboards as non-editable in dashboard json declaration. |
Checks if the remote dashboard has changed, before submitting an update. This prevents the Operator from creating a new version every time a dashboard is reconciled.