-
Notifications
You must be signed in to change notification settings - Fork 897
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
Remove orphaned v2v migration shortcuts #21625
Remove orphaned v2v migration shortcuts #21625
Conversation
Fixes ManageIQ/manageiq-ui-classic#7994 Ironically, they were neglected when we added v2v and added later in commit 53e764f Of course, I missed them when removing v2v in: ManageIQ#21515 Which was part of the larger issue: ManageIQ#21379
@jrafanie we didn't backport the v2v removal right? I still see manageiq-v2v in the upstream/morphy Gemfile |
Correct, v2v is in morphy so no need to backport this. I'll put the morphy/no label just to ensure no one else checks. |
Checked commit jrafanie@f688fa0 with ruby 2.6.3, rubocop 1.13.0, haml-lint 0.35.0, and yamllint |
@jrafanie Technically this needs a data migration as well, if anyone actually chose this as their default shortcut in their user preferences. |
Interesting. Where is this defined in the UI? I'll have to take a look. Note, |
It looks like it works fine NOW after this PR because MiqShortcut has dependent destroy on MiqWidgetShortcut. Before:
After seeding on master:
UI also looks fine now: The "links" shows only the 1 selected miq shortcut, for overview reports |
Fixes ManageIQ/manageiq-ui-classic#7994
Ironically, they were neglected when we added v2v and added later in commit 53e764f
Of course, I missed them when removing v2v in:
#21515
Which was part of the larger issue:
#21379
NOTE: v2v removal wasn't in morphy, so this is morphy/no