You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to use grr diff from a pull point of view?
It seems grizzly is built around making local changes to dashboards and pushing them to grafana, so the grr diff command only shows diffs to files that exist locally.
However we mostly use it for pulling down (automatically via github actions) changes that were made on the UI manually.
When creating new files on the UI, grr diff doesn't see them.
Would it be possible to change this functionality? Or add a flag for this workflow?
The text was updated successfully, but these errors were encountered:
Can you explain further what should be diffed against what? If you make changes via the UI, what resource should that be compared to?
Also, check out the new (not yet released) serve function. This will allow you to edit dashboards that are stored in Git, but using an actual browser window to do the review.
Is there a way to use
grr diff
from a pull point of view?It seems grizzly is built around making local changes to dashboards and pushing them to grafana, so the
grr diff
command only shows diffs to files that exist locally.However we mostly use it for pulling down (automatically via github actions) changes that were made on the UI manually.
When creating new files on the UI,
grr diff
doesn't see them.Would it be possible to change this functionality? Or add a flag for this workflow?
The text was updated successfully, but these errors were encountered: