resilien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

core: ScaleIn should have been ScaleOut 

We are actually acting on/fixing the scale-out here (ie: new child node
from count with no state), not scale-in.
This commit is contained in:
Chris Marchesi 2017-06-22 03:43:05 -07:00
parent f249386c8a
commit 42ebbc6e0e
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
terraform/node_resource_refresh.go
View File

@ -94,7 +94,7 @@ func (n *NodeRefreshableManagedResourceInstance) EvalTree() EvalNode {
switch mode := n.Addr.Mode; mode {
case config.ManagedResourceMode:
if n.ResourceState == nil {
return n.evalTreeManagedScaleInResource()
return n.evalTreeManagedScaleOutResource()
}
return n.evalTreeManagedResource()
@ -173,7 +173,7 @@ func (n *NodeRefreshableManagedResourceInstance) evalTreeManagedResource() EvalN
}
}
func (n *NodeRefreshableManagedResourceInstance) evalTreeManagedScaleInResource() EvalNode {
func (n *NodeRefreshableManagedResourceInstance) evalTreeManagedScaleOutResource() EvalNode {
// Declare a bunch of variables that are used for state during
// evaluation. Most of this are written to by-address below.
var provider ResourceProvider