Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118

I think the format you suggest is awkward in YAML. Because ":" is reserved, you would have to wrap the string in quotes: imports: - this/is/a/string/import.yaml - this is also a string .yaml - "plugins: but here we have to add quotes because of the colon.yaml" The TOSCA way to handle name

Re: get_artifact function usage

ARIA currently supports copying scripts remotely as part of the execution plugin. They are expected to be in the CSAR. But this mechanism is currently totally divorced from the TOSCA artifact structure. On Wed, Sep 20, 2017 at 3:37 AM, D Jayachandran wrote: > Hi

RE: Contribution for https://issues.apache.org/jira/browse/ARIA-118

Hi Tal, With respect to this JIRA issue. I would like to contribute on the first part, which is specific to plugin implementation. " If a plugin contained its plugin.yaml as part of its wagon archive, then once installed, users could import the yaml file more easily using a notation such as

RE: get_artifact function usage

Hi Tal, Thanks for the clarification. When we say download, does the artifact can be at remote location or part of the CSAR ? Regards, DJ -Original Message- From: Tal Liron [mailto:t...@cloudify.co] Sent: Tuesday, September 19, 2017 9:34 AM To: dev@ariatosca.incubator.apache.org