mirror of
https://github.com/letic/terraform-provider-google.git
synced 2024-07-01 15:52:39 +00:00
Update CHANGELOG.md
This commit is contained in:
parent
4f74e3198c
commit
3d976c1d72
|
@ -21,9 +21,14 @@ BUG FIXES:
|
|||
|
||||
## 2.5.0 (April 18, 2019)
|
||||
|
||||
KNOWN ISSUES
|
||||
* compute: `google_compute_subnetwork` will fail to reorder `secondary_ip_range` values at apply time
|
||||
* compute: `google_compute_subnetwork`s used with a VPC-native GKE cluster will have a diff if that cluster creates secondary ranges automatically.
|
||||
|
||||
BACKWARDS INCOMPATIBILITIES
|
||||
* all: This is the first release to use the 0.12 SDK required for Terraform 0.12 support. Some provider behaviour may have changed as a result of changes made by the new SDK version.
|
||||
* compute: `google_compute_instance_group` will not reconcile instances recreated within the same `terraform apply` due to underlying `0.12` SDK changes in the provider. ([#616](https://github.com/terraform-providers/terraform-provider-google/issues/616))
|
||||
* compute: `google_compute_subnetwork` will have a diff if `secondary_ip_range` values defined in config don't exactly match real state; if so, they will need to be reconciled. [GH-3432]
|
||||
* container: `google_container_cluster` will have a diff if `master_authorized_networks.cidr_blocks` defined in config doesn't exactly match the real state; if so, it will need to be reconciled. ([#3427](https://github.com/terraform-providers/terraform-provider-google/issues/3427))
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user