[OASIS Issue Tracker] (TOSCA-155) WD02 - How do we provide constraints on properties declared as simple YAML lists (sets)

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

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

Matthew Rutkowski  edited comment on TOSCA-155 at 11/13/14 3:21 PM:
--------------------------------------------------------------------

Current examples uses       

constraints:
        - min_length: 1

We should also allow max, range as well. 

Describe usage in List type section.

MUSTFIX: certain operators need to include non scalars



was (Author: mrutkows):
Current examples uses       

constraints:
        - min_length: 1

We should also allow max, range as well. 

Describe usage in List type section.


> WD02 - How do we provide constraints on properties declared as simple YAML lists (sets)
> ---------------------------------------------------------------------------------------
>
>                 Key: TOSCA-155
>                 URL: https://issues.oasis-open.org/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 was sent by Atlassian JIRA
(v6.2.2#6258)