[ 
https://issues.apache.org/jira/browse/ARIA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Avia Efrat updated ARIA-338:
----------------------------
    Description: 
According to the TOSCA 1.0 spec, property value should be 'exposed', with the 
same name, as attributes. TOSCA refers to this feature as "refection".
>From the spec, section [3.5.10.1]:

{panel:title=3.5.10.1 Attribute and Property reflection} 
TOSCA orchestrators automatically create Attribute definitions for any Property 
definitions declared on the same TOSCA entity (e.g., nodes, node capabilities 
and relationships) in order to make accessible the actual (i.e., the current 
state) value from the running instance of the entity.
{panel}

  was:
According to the TOSCA 1.0 spec, property value should be 'exposed', with the 
same name, as attributes. TOSCA refers to this feature as "refection".
>From the spec, section [3.5.10.1]:

{panel:title=3.5.10.1 Attribute and Property reflection} 
TOSCA orchestrators automatically create Attribute definitions for any Property 
definitions declared on the same TOSCA entity (e.g., nodes, node capabilities 
and relationships) in order to make accessible the actual (i.e., the current 
state) value from the running instance of the entity.
{noformat}


> Reflect properties as attributes
> --------------------------------
>
>                 Key: ARIA-338
>                 URL: https://issues.apache.org/jira/browse/ARIA-338
>             Project: AriaTosca
>          Issue Type: Story
>    Affects Versions: 0.2.0
>            Reporter: Avia Efrat
>            Priority: Minor
>
> According to the TOSCA 1.0 spec, property value should be 'exposed', with the 
> same name, as attributes. TOSCA refers to this feature as "refection".
> From the spec, section [3.5.10.1]:
> {panel:title=3.5.10.1 Attribute and Property reflection} 
> TOSCA orchestrators automatically create Attribute definitions for any 
> Property definitions declared on the same TOSCA entity (e.g., nodes, node 
> capabilities and relationships) in order to make accessible the actual (i.e., 
> the current state) value from the running instance of the entity.
> {panel}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to