Re: [openstack-dev] [mistral] mistral actions plugin architecture

Hi Filip, Well, it’s not necessary to keep custom action sources as part of Mistral sources. You can keep them anywhere else but the only requirement is that they must be registered globally in python packages so that when Mistral parses entry points in setup.cfg it could find needed classes u

Re: [openstack-dev] [mistral] mistral actions plugin architecture

Thanks for answer! A custom action inherits from base.Action. So if I need to write custom action in different project and register it via entry points then I need dependency on mistral sources. Is that correct? Or is there way how to create custom action without that dependency? Regards Fil

Re: [openstack-dev] [mistral] mistral actions plugin architecture

Hi, It’s pretty simple and described in http://mistral.readthedocs.org/en/master/developer/writing_a_plugin_action.html . Renat Akhmerov @ Mirantis Inc. > On 09 Feb 2015, at 21:43, Filip Blaha wrote: > > Hi al

[openstack-dev] [mistral] mistral actions plugin architecture

Hi all, regarding to [1] there should be some plugin mechanism for custom actions in Mistral. I went through code and I found some introspection mechanism [2] generating mistral actions from methods on client classes for openstack core projects. E.g. it takes nova client class (python-novacli