From 37eaa4abbd941267da895251f88a286476cc6945 Mon Sep 17 00:00:00 2001 From: Modular Magician Date: Tue, 2 Nov 2021 18:21:11 +0000 Subject: [PATCH] Add note on source_ranges tracking changes (#5412) Signed-off-by: Modular Magician --- .changelog/5412.txt | 3 +++ website/docs/guides/version_4_upgrade.html.markdown | 6 ++++++ 2 files changed, 9 insertions(+) create mode 100644 .changelog/5412.txt diff --git a/.changelog/5412.txt b/.changelog/5412.txt new file mode 100644 index 0000000000..8ec013c069 --- /dev/null +++ b/.changelog/5412.txt @@ -0,0 +1,3 @@ +```release-note:none + +``` diff --git a/website/docs/guides/version_4_upgrade.html.markdown b/website/docs/guides/version_4_upgrade.html.markdown index 71e8af6055..e1a87f062d 100644 --- a/website/docs/guides/version_4_upgrade.html.markdown +++ b/website/docs/guides/version_4_upgrade.html.markdown @@ -241,6 +241,12 @@ The provider will now enforce at plan time that one of these fields be set. Previously, if all of these fields were left empty, the firewall defaulted to allowing traffic from 0.0.0.0/0, which is a suboptimal default. +### `source_ranges` will track changes when unspecified in a config + +In `3.X`, `source_ranges` wouldn't cause a diff if it was undefined in +config but was set on the firewall itself. With 4.0.0 Terraform will now +track changes on the block when it is not specified in a user's config. + ## Resource: `google_compute_instance` ### `metadata_startup_script` is no longer set on import