diff options
| author |   James Slagle <jslagle@redhat.com> | 2015-07-09 07:45:54 -0400 |
|---|---|---|
| committer | James Slagle <jslagle@redhat.com> | 2015-07-09 11:19:43 -0400 |
| commit | 9af3ec5865bb78374d0cb669b317eceee266e5c9 (patch) | |
| tree | ff78d2090caab63c27a956a775bc3048fcf1b21b /compute.yaml | |
| parent | 0405a6b248a8328edc1ca050be7e33f436b29c77 (diff) | |
Use parameter_defaults in env files
Switch to using parameter_defaults in environment files instead of a
parameters section. Using a parameters section to set top level
parameters breaks Tuskar based deployments because Tuskar prefixes the
name of the top level parameters with a role name and version, thus
changing the name of the parameter. When the environment file is then
used to set a top level parameter, Heat fails with an error during
template validation:
ERROR: The Parameter (NeutronExternalNetworkBridge) was not defined in template
Change-Id: I605651a8ebdbd0b2baf7bcea198c2988efb55f31
Diffstat (limited to 'compute.yaml')
0 files changed, 0 insertions, 0 deletions