json parameters require json strings rather than accepting arbitrary json structures

[Robert Collins]

e.g. if I have a json parameter foo , in my env file I can do:

Parameters:
   foo: "[ \" A JSON list \" ]"

but not

Parameters:
  foo:
  - A JSON list

Confusingly, I can do:

Parameters:
  foo:
    bar:
    - A list in an object.

[Zane Bitter (zaneb)]

Workaround for now:

  {Fn::Select: [bar, {Ref: foo}]}

This should be an easy fix, but we also really need to switch provider templates over to using the Json parameter type for lists, preferably without breaking any existing templates.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/109357

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/109357
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=f3791a0b450b5851dae43be5a2dffa53b18ee0c1
Submitter: Jenkins
Branch: master

commit f3791a0b450b5851dae43be5a2dffa53b18ee0c1
Author: Ryan Brown <email address hidden>
Date: Thu Jul 24 13:15:15 2014 -0400

    Allow JSON parameters in environment files

    Currently users can specify:
    Parameters:
      foo: "[ \"a\", \"stringified\", \"JSON\", \"list\" ]"

    This change allows:
    Parameters:
      foo:
      - a
      - JSON
      - list

    Change-Id: Ie1616ec4a215f62bc8e06ae2588f953246870b37
    Closes-Bug: #1342487