-
Notifications
You must be signed in to change notification settings - Fork 12.9k
Dashboards: Remove panel plugin provider from migrations #110477
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
Conversation
25: V25, | ||
26: V26, | ||
27: V27, | ||
28: V28(panelProvider), |
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.
Technically we could even refactor v28 migrator to not have be a factory, and follow all the other migrators pattern except the ones with datasources
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.
yes... but i think we will need to refactor all of them to accept context.Context
soon anyway
- Replace hardcoded plugin versions in V24 and V28 migrations with setting.BuildVersion - Add fallback to current dev version (12.2.0-pre) for test environments - Update test expectations and mock plugin versions to match dynamic versioning - Regenerate migration test output files with current versions
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 Ryan!
In #108416, we added a
PanelPluginInfoProvider
to the migrator -- we should avoid this unless it is absolutely necessary and is actually used to migrate the panels.From the current usage it is not necessary and would put real values into an invalid state