[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (TOSCA-155) WD02 - How do we provide constraints on properties declared as simple YAML lists (sets)
[ http://tools.oasis-open.org/issues/browse/TOSCA-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Rutkowski updated TOSCA-155: ------------------------------------- Fix Version/s: CSD2 (was: CSD1) Affects Version/s: CSD2 (was: CSD1) > WD02 - How do we provide constraints on properties declared as simple YAML lists (sets) > --------------------------------------------------------------------------------------- > > Key: TOSCA-155 > URL: http://tools.oasis-open.org/issues/browse/TOSCA-155 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: New Feature > Components: Profile-YAML > Affects Versions: CSD2 > Reporter: Matthew Rutkowski > Assignee: Matthew Rutkowski > Fix For: CSD2 > > > By example, we have the following property defn for tosca.capabilities.Container: > property name: containee_types > required: yes > type: Node Type[] > Description: A list of one or more Node Types that are supported as containees that declare the Container type as a Capability. > Problem 1: how do we constrain list to only include integer types? > Problem 2: how do we constrain list to have at least one valid entry? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]