Currently the plugin paths are hardcoded in the python code. The deployment location of custom plugins might be different than the deployment location of simoorg, so it would be nice to allow the plugin paths to be overriden. My suggested way of doing this would be to add an optional parameter in the fate book to control the search location for plugins:
plugin_base_path: /my/custom/plugin/deployment/location
topology_plugin: MyTopologyPlugin
Currently, I have it working by starting simoorg inside my custom startup script where I override the relevant atropos.*_PLUGIN_PATH global variable, but I'd rather not do this if simoorg supported custom plugin paths out of the box.
Currently the plugin paths are hardcoded in the python code. The deployment location of custom plugins might be different than the deployment location of simoorg, so it would be nice to allow the plugin paths to be overriden. My suggested way of doing this would be to add an optional parameter in the fate book to control the search location for plugins:
Currently, I have it working by starting simoorg inside my custom startup script where I override the relevant
atropos.*_PLUGIN_PATHglobal variable, but I'd rather not do this if simoorg supported custom plugin paths out of the box.