From 6b9f1bf6c0bf99d17e822a9bc39e9b20b4161a31 Mon Sep 17 00:00:00 2001 From: Scott Suarez Date: Tue, 12 Sep 2023 15:49:14 -0700 Subject: [PATCH 1/2] Update version_5_upgrade.html.markdown --- .../website/docs/guides/version_5_upgrade.html.markdown | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/mmv1/third_party/terraform/website/docs/guides/version_5_upgrade.html.markdown b/mmv1/third_party/terraform/website/docs/guides/version_5_upgrade.html.markdown index 88ec1304641f..b238e450c794 100644 --- a/mmv1/third_party/terraform/website/docs/guides/version_5_upgrade.html.markdown +++ b/mmv1/third_party/terraform/website/docs/guides/version_5_upgrade.html.markdown @@ -443,6 +443,15 @@ resource "google_project_iam_binding" "gcs-bucket-writer" { ] } ``` + +## Resource: `google_cloudfunctions2_function` +### `location` now a required field +Deployment would fail if this field was unspecified. Marked this field as requied to align with implementation. This value cannot be inferred from any provider level config. No change is necessary for upgrade as this field is already needed for any deployments. + +## Resource: `google_cloud_run_v2_service` +### transitioned `volumes.cloud_sql_instance.instances` to SET from ARRAY for `google_cloud_run_v2_service` +Previously the API would reorder the user's instances, causing a clientside diff on this field. We've changed to a set implementation to avoid any reordering issues. For upgrading from 4.x you will experience apply/plan diff. After applying the change no further modification is necessary. + ## Product: `cloudiot` ### resource `google_cloudiot_device` is now removed From 7b8b0d7f22a228aec6818b842218aa51affd6d76 Mon Sep 17 00:00:00 2001 From: Scott Suarez Date: Wed, 13 Sep 2023 15:39:09 -0700 Subject: [PATCH 2/2] Update mmv1/third_party/terraform/website/docs/guides/version_5_upgrade.html.markdown --- .../website/docs/guides/version_5_upgrade.html.markdown | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/mmv1/third_party/terraform/website/docs/guides/version_5_upgrade.html.markdown b/mmv1/third_party/terraform/website/docs/guides/version_5_upgrade.html.markdown index b238e450c794..ea8677a03b5c 100644 --- a/mmv1/third_party/terraform/website/docs/guides/version_5_upgrade.html.markdown +++ b/mmv1/third_party/terraform/website/docs/guides/version_5_upgrade.html.markdown @@ -450,7 +450,9 @@ Deployment would fail if this field was unspecified. Marked this field as requie ## Resource: `google_cloud_run_v2_service` ### transitioned `volumes.cloud_sql_instance.instances` to SET from ARRAY for `google_cloud_run_v2_service` -Previously the API would reorder the user's instances, causing a clientside diff on this field. We've changed to a set implementation to avoid any reordering issues. For upgrading from 4.x you will experience apply/plan diff. After applying the change no further modification is necessary. +Previously, `database_flags` was a list, making it order-dependent. It is now a set. + +If you were relying on accessing an individual flag by index (for example, `google_sql_database_instance.instance.settings.0.database_flags.0.name`), then that will now need to by hash (for example, `google_sql_database_instance.instance.settings.0.database_flags..name`). ## Product: `cloudiot`