[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-274) get_property syntax is not valid
[ https://issues.oasis-open.org/browse/TOSCA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60601#comment-60601 ] Luc Boutier commented on TOSCA-274: ----------------------------------- Document added for proposal. Proposal in the doc also solves TOSCA-231 https://www.oasis-open.org/apps/org/workgroup/tosca/document.php?document_id=56361 > get_property syntax is not valid > -------------------------------- > > Key: TOSCA-274 > URL: https://issues.oasis-open.org/browse/TOSCA-274 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: Bug > Components: Profile-YAML, Spec - Simple Profile > Reporter: Luc Boutier > Priority: Blocker > > There is currently a big issue with the syntax of get_property, having an optional parameter as a second parameter with all parameters being of the same type is really bad practice. > Let's consider a node: > node: > properties: > toto: > type: my_complex > capabilities: > toto: > properties: > titi: > type: string > Let's say that the my_complex type has a titi field that is a string. > What do we do when we encounter a get_property that is: > get_property["node", "toto", "titi"] > Are we getting the toto's property nested field ? or the titi property of toto capability ? -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]