provider/google Fix backend service max_utilization attribute

Fixes issue #4985 by correcting copy/paste error that caused the
max_utilization attribute to be read from the max_rate_per_instance
attribute.

N.B. There is still no test coverage for this issue.
This commit is contained in:
Bill Fumerola 2016-02-03 19:06:32 -08:00
parent c628dd9247
commit 6fa4fba83e
2 changed files with 2 additions and 1 deletions

View File

@ -33,6 +33,7 @@ BUG FIXES:
* provider/cloudflare: `ttl` no longer shows a change on each plan on `cloudflare_record` resources [GH-5042] * provider/cloudflare: `ttl` no longer shows a change on each plan on `cloudflare_record` resources [GH-5042]
* provider/aws: Fix reading auto scaling group load balancers [GH-5045] * provider/aws: Fix reading auto scaling group load balancers [GH-5045]
* provider/aws: Fix reading auto scaling group availability zones [GH-5044] * provider/aws: Fix reading auto scaling group availability zones [GH-5044]
* provider/google: Fix backend service max_utilization attribute [GH-4895]
## 0.6.11 (February 1, 2016) ## 0.6.11 (February 1, 2016)

View File

@ -300,7 +300,7 @@ func expandBackends(configured []interface{}) []*compute.Backend {
if v, ok := data["max_rate_per_instance"]; ok { if v, ok := data["max_rate_per_instance"]; ok {
b.MaxRatePerInstance = v.(float64) b.MaxRatePerInstance = v.(float64)
} }
if v, ok := data["max_rate_per_instance"]; ok { if v, ok := data["max_utilization"]; ok {
b.MaxUtilization = v.(float64) b.MaxUtilization = v.(float64)
} }