OS::Heat::Value json type should accept lists

[Steven Hardy]

A Json parameter type accepts the following:

- map
- list
- json string (serializing either a map or a list)

It seems like the OS::Heat::Value resource is more restrictive, which can be confusing, as e.g trying to pass a list with type: json results in an error like:

heat.common.exception.StackValidationFailed: Property error: resources.my_value.properties.value: "[u'a', u'Z', u'B', u'y']" is not a map

The workaround is to use comma_delimited_list, but it'd be nice to make this consistent with how the Json parameter validation works.

[Zane Bitter (zaneb)]

Good catch, it would be nice to fix that.

The reaaon is that although it's using the parameter names for stuff, internally it's converting that to the property constraints. I wonder if it's possible to use a parameters.Schema object in place of a properties.Schema one in a Property without any side-effects...