-
Notifications
You must be signed in to change notification settings - Fork 251
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
Do not delete dashboard uid fields #136
Conversation
I believe this also causes weird folder issues (a duplicate gets placed into |
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.
Change makes sense to me, but it's causing some acceptance tests to fail (really need to add those to CI).
a58dc41
to
9cd1a09
Compare
You are right. I rebased and updated the acceptance tests to include the Now only the acceptance test that was failing before this PR is still failing:
|
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.
Thanks!
Hi! Does this mean that the |
The purpose of the
uid
field is to allow migrating dashboards between Grafana instances and provisioning Grafana from configuration without breaking references. From my understanding this field is not instance-specific (such asid
), therefore it should be preserved.