Feature #4175
open
Possibility to enable/disable plugin via runtime
Description
Users should be able to enable or disable plugins in the About screen.
We do not want runtime plugin booting of course, just making note somewhere (db?) that a plugin is disabled, so it won't load during next restart. This would be handy for upgrades, where we could ask users to disable all thirdparty (not-supported) plugins prior upgrade.
We could also add new column "supported: yes/no" to plugin metadata, so we can present easily which of these are fully supported (distributed in our repos - upgradable).
Updated by Dominic Cleal over 10 years ago
If this is technically possible to disable plugins, then we should link it to the "requires_foreman" version check so we can avoid loading plugins that are incompatible. I'm unsure at the moment how much this prevents loading of the plugin, and/or the application.
Supported yes/no could be done via the author perhaps? e.g. the authors today are individuals, when we really could say for stuff hosted in our GitHub organisation that the author should be set to "The Foreman", "Foreman Team", "theforeman.org" or similar.
Updated by Lukas Zapletal about 10 years ago
That's right, supported column could be misleading, if we should author on the about page, we can instruct users to disable all non-Foreman provided plugins prior upgrade.