Re: get_artifact function usage

Sorry, I forgot to answer this. The answer is not good: sadly, there is no solid support for artifacts in ARIA right now beyond parsing. This function is currently a no-op. Rather than just implement this function, I think it should be tackled as part of comprehensive support for artifacts:

Re: Use & impact of role/host attribute in ARIA

Feel free to take over the JIRA issue. :) On Mon, Sep 18, 2017 at 10:50 PM, D Jayachandran < d.jayachand...@ericsson.com> wrote: > Hi Tal, > > This seems to be a better option and we can contribute for it. > > > Regards, > DJ > > -Original Message- > From: Tal Liron

RE: get_artifact function usage

Hi, Do we have any comments on this ? Regards, DJ -Original Message- From: D Jayachandran [mailto:d.jayachand...@ericsson.com] Sent: Thursday, September 14, 2017 4:20 PM To: dev@ariatosca.incubator.apache.org Cc: Vaishnavi K.R ; Vaishali Krishnamurthy

RE: Use & impact of role/host attribute in ARIA

Hi Tal, This seems to be a better option and we can contribute for it. Regards, DJ -Original Message- From: Tal Liron [mailto:t...@cloudify.co] Sent: Monday, September 11, 2017 9:26 PM To: dev@ariatosca.incubator.apache.org Subject: Re: Use & impact of role/host attribute in ARIA I

Re: Property type 'null' validation issue

This does sound like a bug, and I am not familiar with a JIRA ticket for it. Feel free to create one. On Mon, Sep 18, 2017 at 8:13 AM, Vaishnavi K.R wrote: > Hi, > > > I tried using the 'null' property type as mentioned in the TOSCA simple > YAML 1.0 specification.

Re: Unique identification of an instance element across services

The service name is optional - it may be auto-generated according to the service-template name. The service-template name can also be made optional (see this jira issue: https://issues.apache.org/jira/browse/ARIA-221 ). Regarding the scenario of non-CLI interaction - for any non-human usage,

Re: Unique identification of an instance element across services

Hi All, In addition to the node instance name, I am concerned about the service template name and the service instance names. In a wider perspective, there is high chance for these names to be the same. And as I have already mentioned in previous discussion, its an overhead for an user to