[ 
https://issues.apache.org/jira/browse/ARIA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006758#comment-16006758
 ] 

ASF subversion and git services commented on ARIA-139:
------------------------------------------------------

Commit 60ea3ebb21e762d36115db26563a93dd3cb72003 in incubator-ariatosca's branch 
refs/heads/master from [~emblemparade]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-ariatosca.git;h=60ea3eb ]

ARIA-139 Support attributes

* Fully implement attribute support in parser
* New intrinsic function evaluation mechanism
* Implemented more intrinsic functions, including get_attribute
* Fix to one-on-one relationship back population
* Fixes to TOSCA use case examples
* Indirectly related: re-enabled node_filter mechanism and reworked
filter constraints in order to make them serializable
* utils/type is much more robust now and consolidates all conversions
and names
* Moved dsl_specification to new utils/specification (because utils/type
uses it)


> TOSCA attributes
> ----------------
>
>                 Key: ARIA-139
>                 URL: https://issues.apache.org/jira/browse/ARIA-139
>             Project: AriaTosca
>          Issue Type: Story
>            Reporter: Tal Liron
>            Assignee: Tal Liron
>
> This feature needs to work in the parser, in modeling, and for the intrinsic 
> function {{get_attribute}}.
> We also need to find a way to relate existing {{runtime_properties}} to this 
> feature.
> We should convert our code that uses {{state}} field in nodes to use the 
> {{state}} attribute instead.
> We need to set the {{tosca_id}} and {{tosca_name}} attributes.
> We should use the {{public_address}} and {{private_address}} attributes 
> instead of the {{host_address}} property.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to