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:`.
Reviewed: https:/ /review. openstack. org/303305 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=a12087715f0 fe4251a95ab6712 0023d553c24a45
Committed: https:/
Submitter: Jenkins
Branch: master
commit a12087715f0fe42 51a95ab67120023 d553c24a45
Author: Jiri Stransky <email address hidden>
Date: Fri Apr 8 10:59:07 2016 +0200
Always use parameter_defaults in environment files
In the environments/ subdirectory of tripleo- heat-templates, we mostly defaults` .
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_
This commit switches all `parameters:` uses in environments/ defaults: `.
subdirectory to `parameter_
Change-Id: Ie4c03c7e7f5a50 04a0384d3581713 5f357e9719b
Closes-Bug: #1567837