Parser does not parse correctly complex node properties

[Denis Makogon]

Assume you have next node:

    orchestra_security_group:
      type: tosca.openstack.security_group
      properties:
        name_or_id: { get_input: compute_name }
        description: { get_input: compute_name }
        rules:
          - direction: 'ingress'
            ethertype: 'IPv4'
            port_range_min: 1
            port_range_max: 65535
            protocol: 'tcp'
            remote_ip_prefix: '0.0.0.0/0'
      requirements:
        - authorization_form: auth

And now as user i want to make it parametrized:

    orchestra_security_group:
      type: tosca.openstack.security_group
      properties:
        name_or_id: { get_input: compute_name }
        description: { get_input: compute_name }
        rules:
          - direction: { get_input: direction }
            ethertype: { get_input: ethertype }
            port_range_min: { get_input: port }
            port_range_max: { get_input: port }
            protocol: { get_input: protocol }
            remote_ip_prefix: { get_input: cidr }
      requirements:
        - authorization_form: auth

Having the assumption that parser should recursively setup property values with TOSCA functions, but it appears, that parser is not doing such, just defining property with '{ get_input: direction }' string as value.

So, as it can be seen, property 'rule' is a property of 'list' type and parser should be aware of how to parse properties of type 'map' and 'list'.