Steve, we cannot change the TOSCA spec, and the spec does not say anything about naming conventions here.
I think, though, that an obvious part of this JIRA will be to emit an error if an attribute name is the same as a property name, because obviously this would break this feature. On Thu, Nov 16, 2017 at 2:12 PM, Steve Baillargeon < steve.baillarg...@ericsson.com> wrote: > I see the following text in the JIRA: > According to the TOSCA 1.0 spec, property value should be 'exposed', with > the same name, as attributes. > > Does the spec really say to use the same name? As far as I know it does > not. > What about using a better reflected attribute naming convention like > “actual_<property_name>”? > Can I add this to the JIRA? > > -Steve B > > -----Original Message----- > From: Tal Liron [mailto:t...@cloudify.co] > Sent: Thursday, November 16, 2017 2:48 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Attribute and Property Reflection > > Not right now, but there is an open JIRA to support it. > > On Thu, Nov 16, 2017 at 1:42 PM, Steve Baillargeon < > steve.baillarg...@ericsson.com> wrote: > > > Hi > > Does ARIA support "attribute and property reflection" defined in > 3.5.10.1? > > > > Regards > > Steve B > > > > >
