Always use parameter_defaults in environment files
authorJiri Stransky <jistr@redhat.com>
Fri, 8 Apr 2016 08:59:07 +0000 (10:59 +0200)
committerDan Prince <dprince@redhat.com>
Mon, 11 Apr 2016 18:15:39 +0000 (14:15 -0400)
commita12087715f0fe4251a95ab67120023d553c24a45
tree6a9514b351b581e2ea824fe07fbd507ae9587766
parent0970068cbb49d7c4dde6eb2e324058f9b4652c6d
Always use parameter_defaults in environment files

In the environments/ subdirectory of tripleo-heat-templates, we mostly
use parameter_defaults, but some of the environment files still use
parameters. This can lead to confusing behavior with respect to
parameter priority when passing environment files to deploy/update
commands. Users might expect that subsequent environment files take
priority over preceding ones, but that might not be the case if the
preceding environment files use `parameters`, while the subsequent ones
use `parameter_defaults`.

This commit switches all `parameters:` uses in environments/
subdirectory to `parameter_defaults:`.

Change-Id: Ie4c03c7e7f5a5004a0384d35817135f357e9719b
Closes-Bug: #1567837
environments/docker.yaml
environments/manage-firewall.yaml
environments/mongodb-nojournal.yaml
environments/puppet-ceph-devel.yaml
environments/puppet-tenant-vlan.yaml
environments/updates/update-from-keystone-admin-internal-api.yaml