From 3e35fb9c0506dd5d0540de90b1db3d9e5e02ed01 Mon Sep 17 00:00:00 2001 From: Dana Hoffman Date: Tue, 12 Nov 2019 17:55:12 -0800 Subject: [PATCH] Add upgrade note for IoT registry event_notification_configs (#2390) (#2651) Merged PR #2651. --- .../guides/version_3_upgrade.html.markdown | 34 +++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/third_party/terraform/website/docs/guides/version_3_upgrade.html.markdown b/third_party/terraform/website/docs/guides/version_3_upgrade.html.markdown index 17460ed8cad7..0522695cff5e 100644 --- a/third_party/terraform/website/docs/guides/version_3_upgrade.html.markdown +++ b/third_party/terraform/website/docs/guides/version_3_upgrade.html.markdown @@ -373,6 +373,40 @@ documentation. In an attempt to avoid allowing empty blocks in config files, `public_key_certificate` is now required on the `google_cloudiot_registry.credentials` block. +### Replace singular event notification config field with plural `event_notification_configs` + +Use the plural field `event_notification_configs` instead of +`event_notification_config`, which has now been removed. +Since the Cloud IoT API now accept multiple event notification configs for a +registry, the singular field no longer exists on the API resource and has been +removed from Terraform to prevent conflicts. + + +#### Old Config + +```hcl +resource "google_cloudiot_registry" "myregistry" { + name = "%s" + + event_notification_config { + pubsub_topic_name = "${google_pubsub_topic.event-topic.id}" + } +} + +``` + +#### New Config + +```hcl +resource "google_cloudiot_registry" "myregistry" { + name = "%s" + + event_notification_configs { + pubsub_topic_name = "${google_pubsub_topic.event-topic.id}" + } +} +``` + ## Resource: `google_composer_environment` ### `use_ip_aliases` is now required on block `google_composer_environment.ip_allocation_policy`