Closed videlanicolas closed 2 years ago
This is interesting: https://registry.terraform.io/modules/sysdiglabs/secure-for-cloud/google/latest#q-getting-error-creating-topic-googleapi-error-409-resource-already-exists-in-the-project-resourcegcr
This error happens due to a GCP limitation where only a single topic named gcr can exist. This name is [gcp hardcoded](https://cloud.google.com/container-registry/docs/configuring-notifications#create_a_topic) and is the one we used to detect images pushed to the registry.
I'll apply the workaround and try again.
Seems like I had to manually import the config in place as specified by the link above.
While setting up a new GCP project I got the following error:
Not sure why Terraform complains about the resource already existing? Shouldn't Terraform make sure the configured state is reflected in the GCP project?