Merge pull request #7086 from glasser/patch-2
Mention in CHANGELOG that var.map.key doesn't work
This commit is contained in:
commit
9a986f88a3
|
@ -13,6 +13,7 @@ BACKWARDS INCOMPATIBILITIES / NOTES:
|
||||||
and reference the security groups by their `id`.
|
and reference the security groups by their `id`.
|
||||||
Ref https://github.com/hashicorp/terraform/issues/6416#issuecomment-219145065
|
Ref https://github.com/hashicorp/terraform/issues/6416#issuecomment-219145065
|
||||||
* `aws_route53_record`: `latency_routing_policy`, `geolocation_routing_policy`, and `failover_routing_policy` block options have been added. With these additions we’ve renamed the `weight` attribute to `weighted_routing_policy`, and it has changed from a string to a block to match the others. Please see the updated documentation on using `weighted_routing_policy`: https://www.terraform.io/docs/providers/aws/r/route53_record.html . [GH-6954]
|
* `aws_route53_record`: `latency_routing_policy`, `geolocation_routing_policy`, and `failover_routing_policy` block options have been added. With these additions we’ve renamed the `weight` attribute to `weighted_routing_policy`, and it has changed from a string to a block to match the others. Please see the updated documentation on using `weighted_routing_policy`: https://www.terraform.io/docs/providers/aws/r/route53_record.html . [GH-6954]
|
||||||
|
* You now access the values of maps using the syntax `var.map["key"]` or the `lookup` function instead of `var.map.key`.
|
||||||
|
|
||||||
FEATURES:
|
FEATURES:
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue