Parameters have to have only different names

[Sergey Kraynev]

Currently you could define template with parameters, which have same names.
However as result you will get only second definition of this parameter.
I think that it's incorrect behavior and should be caught during validation.

[Clint Byrum (clint-fewbar)]

http://pyyaml.org/ticket/128

Detecting duplicate map keys is non-trivial.. I'm not sure it is appropriate to target this as something we can handle soon.

[Sergey Kraynev (skraynev)]

Clint, I have looked this issue. It's very long time problem. However now it has high status for fixing.
From other side JSON has same problem and according to rfc " ...The names within an object SHOULD be unique..."
If in the first case (yaml) problem will be fixed "soon", we still have problem with second case (json).
I think, that will be good to make some workaround when we parse template:

 - For JSON, we could use such approach https://mail.python.org/pipermail/python-list/2013-May/647954.html
 - For YAML, it does not work, unfortunately. So we could use weird hack:
parse yaml template -> take first name of resource (or parameter, or output) and count the numbers of this name in parsed template (just transform it in string) and repeat it for unparsed template -> compare numbers in both cases.
But IMO, I prefer to wait fix from yaml project =)

[Steven Hardy (shardy)]

No fix proposed so bumping to J3

[Clint Byrum (clint-fewbar)]

Removing milestone altogether. Sergey has said he'd like to wait for a proper fix from pyyaml, and I agree. The auto-link _might_ actually work and tell us if that bug is fixed upstream.