-
Notifications
You must be signed in to change notification settings - Fork 900
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
Chopping Block ✂️ 🔥 #21377
Comments
I'll open up individual issue for the ones we agreed on |
I added FileDepot to the OP. I believe the only thing it is still used for is log collection, but I'm wondering if we can do log collections completely differently and then just completely delete this class. Let's discuss. |
Added discussion for the removal of "Menu" widgets. These seem completely pointless to me, but maybe I'm misunderstanding some fundamental thing. cc @GilbertCherrie |
can chop Also, in the pod world, I do not think that the customer is even able to modify the But this is a business feature and it may be used. |
@Fryguy Removed live metrics in ManageIQ/manageiq-ui-classic#8093 |
Log Collection code deletion is being handled here ManageIQ/manageiq-ui-classic#8235 |
I think we still have code that depends on the FileDepot via the FileDepotMixin.
I think we can delete the LogFile first and then tackle removing the FileDepotMixin. I'm not familiar with the PxeServer code to know if that depot code can be removed at this time. |
Note, I would love to just delete the FileDepot but I think the PxeServer code is still using parts of the FileDepot via the following calls to
|
Note, as I look at this more, FileDepot and subclasses seem to be unrelated to the FileDepotMixin module other than the name being similar. FileDepotMixin is using 'mount/miq_generic_mount_session' to mount a NFS/SMB/FTP/etc. session and then using that to upload/download/delete files. This is what PxeServer is using. The LogFile class is using FileDepot and subclasses with explicit rows in the database. FileDepot and subclasses seem to be used for LogFiles, schedules, and MiqServers. We might be able to detangle that and remove the FileDepot and subclasses if PxeServer and FileDepotMixin don't require FileDepot. But for now, I think LogFile is completely safe to remove. |
@jrafanie @kbrock @agrare @MelsHyrule As discussed, I added #22365 to the Chopping Block |
per stale, I added #22642 (based upon a NickL PR that is simple but requires migrations that possibly hit a number of tables) |
Some old Transform VM cleanup: #21874 |
This issue is a list of candidates for removal or serious refactoring due to limited demand of the feature crossed with level of effort in maintenance / footprint
Complete removal:
Possible archiving:
Refactoring / Fixes:
Needs more discussion
Other things discussed for removal and NAK'd
The text was updated successfully, but these errors were encountered: