[Roadmap] Plugin Improvements

[SchrodingersGat]

From issues identified in #5624

Plugin Features / Improvements

[tasklist]

Plugin Tasks

• Fix bug in "install plugin" API endpoint where failure is not correctly reported - Fix for plugin installation via web interface #5646
• Automatically reload plugin registry when plugins change in another running worker - Plugin reload mechanism #5649
• Automatically run migrations when a new plugin is activated - Plugin auto migrate #5668
• Improve plugin reload mechanism with mutex locking - Plugin reload mechanism #5649
• Enable plugin list API to be filtered by "builtin" or "sample" status - Allow plugin list to be filtered by "sample" or "builtin" status #5647
• Cleanup "old" plugin configs (which reference plugins which are no longer available on the system) - Plugin clean config #5652
• Automatically reload plugin registry when the plugin settings change - Allow reload of plugin registry when config changes #5662
• Provide users with better feedback if a plugin requires features which are not enabled (like app-mixin / url-mixin / etc)
• Inform users when the system has unapplied migrations (if they are not applied automatically)
• Collect more metadata for plugins which are not installed
• Check for available plugin updates periodically - e.g. https://pypi.org/project/pip-check-updates/

[matmair]

Not sure collection of more metadata is possible without running into serious security problems.

[SchrodingersGat]

Not sure collection of more metadata is possible without running into serious security problems.

It may not be. I'd like to look into it but it doesn't look likely

[matmair]

Would be amazing if there were a way, I am just not aware of one.

[wolflu05]

If there is no other way, the only thing I see is parsing the setup.py/plugin file without executing it, by converting it to an AST with pythons ast module.

[30350n]

If there is no other way, the only thing I see is parsing the setup.py/plugin file without executing it, by converting it to an AST with pythons ast module.

This is exactly how Blender does it for Python addons. Each addon has to contain a static bl_info section, like this for example, which can be parsed like that. The actual addon code will only be executed once you enable the addon.

[SchrodingersGat]

@30350n thanks for the info! And very nice looking plugin too. Might have to use that myself