[OASIS Issue Tracker] (TOSCA-204) Parameter definitions on operations should be closer to property definitions

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/TOSCA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59288#comment-59288 ] 

Luc Boutier commented on TOSCA-204:
-----------------------------------

Specification has changed and inputs of operations can now be either a property assignment or property definitions solving the issue.

Motion has passed to close the issue on 26/03/2015 meeting.

> Parameter definitions on operations should be closer to property definitions
> ----------------------------------------------------------------------------
>
>                 Key: TOSCA-204
>                 URL: https://issues.oasis-open.org/browse/TOSCA-204
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>            Reporter: Luc Boutier
>
> We should allow definition of constraints on parameters in case they are not bound to properties.
> I am here thinking to custom interfaces extensions rather to the normative interfaces as I think some orchestrator may want to provide a feature to run custom interfaces operations on running node instances.
> In such situations providing parameters in an UI (with constraint validation) may be a nice feature. In order to do so the spec should allow providing constraints to an operation parameter.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)