Hi While the investigation is on-going, I need to double check what can be done today. But I guess how it is done today might change as well (?) Based on our analysis of the latest code base, the loading of the custom workflows today is from CSAR only. Please advise.
-Steve -----Original Message----- From: Tal Liron [mailto:[email protected]] Sent: Tuesday, November 28, 2017 2:06 PM To: [email protected] Subject: Re: Loading Custom Workflows from CSAR Thanks, Steve. We don't have a JIRA for this right now, but we do intend to have a way to include "plugins" in a CSAR and have them automatically installed. A "plugin" is basically a Python extension to ARIA that can be loaded at runtime and contained per service. This is part of our current general work trying to find a good design for plugins generally, and will likely result in a JIRA epic with several issues. At this time, I don't think it's worth created this epic if we don't have a plan. The design will likely be inspired by the plugin design in Cloudify, from which we grabbed our seed code. However, there is room for some re-imagination especially as pertains TOSCA-specific issues. On Tue, Nov 28, 2017 at 1:01 PM, Steve Baillargeon < [email protected]> wrote: > Hi > As far as I know the implementation string associated with the > aria.Workflow type must call or execute a Python function (using the > dot > notation) that is stored in ARIA, like a plugin. > When will it be possible to refer to a .py file stored in the CSAR > instead? > Do you have any Jira for this enhancement? > > Regards > Steve B >
