Jiri Stransky fbc435ce16 Only use parameter_defaults for scaling down ... We were using parameters for scaling down but parameter_defaults for scaling up. The old parameters from scale-down still persisted in the stack and took precedence over the scaled-up parameter_defaults, so the scaled-up values didn't propagate. We already update parameter_defaults in the deployment plan in that same method, so all we need to do is remove the 'parameters' part. Change-Id: I90a195a66b15c7c9057bfb415b6a730bbd9a939c Closes-Bug: #1641142		2016-11-11 18:43:00 +01:00
..
__init__.py	Initial Integration of Mistral into TripleO	2016-05-16 09:15:14 -04:00
baremetal.py	Support node untagging	2016-10-05 09:50:23 -03:00
base.py	Sets defaults in swift connection related to retries	2016-11-02 17:33:07 -04:00
deployment.py	Check the result of the parent action when subclassing	2016-09-15 15:25:58 +01:00
heat_capabilities.py	Include environments in capabilities output	2016-09-02 12:23:20 +01:00
parameters.py	Use parameters from existing Heat stack if it already exists	2016-11-04 16:34:08 +00:00
plan.py	Clearer error when the Mistral env already exists	2016-09-12 16:55:37 +01:00
scale.py	Only use parameter_defaults for scaling down	2016-11-11 18:43:00 +01:00
templates.py	Default the J2 excludes files to safe values.	2016-10-11 21:36:13 +02:00
validations.py	Merge "Handle missing mistral environment"	2016-09-19 09:09:52 +00:00