Ran Ziv created ARIA-235:
----------------------------
Summary: Custom workflow code delivery mechanism
Key: ARIA-235
URL: https://issues.apache.org/jira/browse/ARIA-235
Project: AriaTosca
Issue Type: Story
Reporter: Ran Ziv
Priority: Trivial
To use custom workflows, users currently have to have the custom workflow code
as part of their service-template package.
We need to review if this is the sensible way for users to deliver custom
workflows, noting that there's already a mechanism for delivering code which is
the plugins mechanism - Supposedly, users could deliver workflows code this way
instead if that makes sense in the context of workflow authors, or possibly we
could support both methods.
If it were to behave like plugins, it would require the workflow execution
environment to be more isolated (see related JIRA ARIA-234) since it'd involve
installation of packages (although, unlike operation plugins, workflows
shouldn't [but may] require additional libraries and dependencies of their own).
Regardless of whether we'd support delivering workflows code via the plugin s
mechanism, if we're to continue supporting the current method of delivery (i.e.
via the service-template's package) then the implementation in
{{WorkflowRunner}} needs to change as it currently assumes the resource-storage
to necessarily be a {{FileSystemResourceAPI}} and adds the service-template's
resources path directly. It should instead retrieve the necessary resources and
have them in the PATH.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
