You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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_PATH global variable, but I'd rather not do this if simoorg supported custom plugin paths out of the box.
The text was updated successfully, but these errors were encountered:
Hey @srikanth-viswanathan, Just wanted to see if you are actively working on the current issues that you raised with Simoorg. they seem to be really nice suggestions. Let me know :)
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_PATH
global variable, but I'd rather not do this if simoorg supported custom plugin paths out of the box.The text was updated successfully, but these errors were encountered: