From ce09c07ced1bacff483fdb2eb5a37872c8e97f2f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Beno=C3=AEt=20Sauv=C3=A8re?= Date: Fri, 11 Oct 2024 11:41:05 +0200 Subject: [PATCH] fix(artifact-registry): fix a move issue with tf>1.7 (#2617) The TF 1.8 has introduced a new feature that makes the move failing: > Providers can now transfer the ownership of a remote object between resources of different types, for situations where there are two different resource types that represent the same remote object type. > This extends the moved block behavior to support moving between two resources of different types only if the provider for the target resource type declares that it can convert from the source resource type. Refer to provider documentation for details on which pairs of resource types are supported. https://github.com/hashicorp/terraform/blob/v1.8/CHANGELOG.md#180-april-10-2024 --- modules/artifact-registry/iam.tf | 1 + 1 file changed, 1 insertion(+) diff --git a/modules/artifact-registry/iam.tf b/modules/artifact-registry/iam.tf index 62b0dff63..da0c78df7 100644 --- a/modules/artifact-registry/iam.tf +++ b/modules/artifact-registry/iam.tf @@ -20,6 +20,7 @@ moved { } resource "google_artifact_registry_repository_iam_binding" "authoritative" { + provider = google-beta for_each = local.iam project = var.project_id location = google_artifact_registry_repository.registry.location