[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-204) Parameter definitions on operations should be closer to property definitions
[ https://issues.oasis-open.org/browse/TOSCA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luc Boutier updated TOSCA-204: ------------------------------ Component/s: Profile-YAML > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]