gistfile1.txt

$ terraform apply --auto-approve
data.google_project.current: Reading...
google_kms_crypto_key.containers-local-dev: Refreshing state... [id=projects/XXX/locations/us-central1/keyRings/artifacts_us-central1/cryptoKeys/containers-local-dev]
data.google_project.current: Read complete after 0s [id=projects/XXX]
google_kms_crypto_key_iam_member.containers-local-dev: Refreshing state... [id=projects/XXX/locations/us-central1/keyRings/artifacts_us-central1/cryptoKeys/containers-local-dev/roles/cloudkms.cryptoKeyEncrypterDecrypter/serviceAccount:service-1048847563382@gcp-sa-artifactregistry.iam.gserviceaccount.com]
module.artifact_registry.google_artifact_registry_repository.repo: Refreshing state... [id=projects/XXX/locations/us-central1/repositories/containers-local-dev]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the
following symbols:
  + create

Terraform will perform the following actions:

  # module.artifact_registry.google_artifact_registry_repository_iam_member.writers["group:engineering-team@XXX.com"] will be created
  + resource "google_artifact_registry_repository_iam_member" "writers" {
      + etag       = (known after apply)
      + id         = (known after apply)
      + location   = "us-central1"
      + member     = "group:engineering-team@XXX"
      + project    = "XXX"
      + repository = "containers-local-dev"
      + role       = "roles/artifactregistry.writer"
    }

Plan: 1 to add, 0 to change, 0 to destroy.
module.artifact_registry.google_artifact_registry_repository_iam_member.writers["group:engineering-team@XXX"]: Creating...
╷
│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to
│ module.artifact_registry.google_artifact_registry_repository_iam_member.writers["group:engineering-team@XXX"],
│ provider "provider[\"registry.terraform.io/hashicorp/google\"]" produced an unexpected new value: Root resource was present,
│ but now absent.
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.