parameter_defaults only apply to nested stacks

I think parameter_defaults should work for the top-level stack too, that it doesn't is probably an oversight given that the main focus was on nested stacks when it got implemented.

For now I guess something like a yaml reference between parameters and parameter_defaults in the environment may be a workaround?

I'll look into a fix.

Hmm, so I've just tested with latest master and I can't currently reproduce this:

-bash-4.3$ cat parent.yaml
heat_template_version: 2013-05-23
parameters:
  foo:
    type: number
resources:
  random:
    type: OS::Heat::RandomString
    properties:
        length: {get_param: foo}

-bash-4.3$ cat env.yaml
parameter_defaults:
    foo: 3

heat stack-create p3 -f parent.yaml -e env.yaml

$ heat resource-show p3 random
+------------------------+-------------------------------------------------------------------------------------------------------------------------------------+
| Property | Value |
+------------------------+-------------------------------------------------------------------------------------------------------------------------------------+
| attributes | { |
| | "value": "6FI" |
| | }

So, AFAICT this is working as required?

AFAIK this has now been proven to work, e.g https://review.gerrithub.io/#/c/243608/ so marking invalid.

Turns out this is not invalid, but the problem only affects json and comma_delimited_list parameters:

https://review.openstack.org/#/c/234055/

Kudos to jistr for discovering this!

I'm going to close this a duplicate of 1504137 (even though that was reported later), because that's got a patch under review already, which I think we can work to resolve both issues (e.g fix both parameter types).