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
The numerical folderId is included in the grizzly resources created with grr pull. This seems unnecessary given the existence of the folderUid. Including folderId in the diff causes there to always be a diff when using the same grizzly resource to manage multiple Grafana instances. Example of a LibraryElement:
Grafana A
$ grr diff panel-a1c2a383-9319-4216-9967-101de787a7b7.yaml
INFO Diff-ing 1 resources
LibraryElement.a1c2a383-9319-4216-9967-101de787a7b7 no differences
If I remove folderId from the yaml file, It shows up as a remove in the diff on both Grafanas.
My gut says the diff shouldn't consider the numerical folderId since the folderUid exists and can be set the same on multiple Grafana instances. I'd be happy for any other solution that reduces this unnecessary noise too.
The text was updated successfully, but these errors were encountered:
Feature Request
The numerical
folderId
is included in the grizzly resources created withgrr pull
. This seems unnecessary given the existence of thefolderUid
. IncludingfolderId
in the diff causes there to always be a diff when using the same grizzly resource to manage multiple Grafana instances. Example of a LibraryElement:Grafana A
Grafana B
If I remove
folderId
from the yaml file, It shows up as a remove in the diff on both Grafanas.My gut says the diff shouldn't consider the numerical
folderId
since thefolderUid
exists and can be set the same on multiple Grafana instances. I'd be happy for any other solution that reduces this unnecessary noise too.The text was updated successfully, but these errors were encountered: