Open jeremad opened 2 months ago
Hi @jeremad please share the output that you got after running the terraform import google_clouddomains_registration.example
Also confirm if you are using only the command terraform import google_clouddomains_registration.example
or this other one terraform import google_clouddomains_registration.example xxx.yyy
Here is the output:
...
google_clouddomains_registration.example: Import prepared!
Prepared google_clouddomains_registration for import
...
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
Here is the command:
terraform import google_clouddomains_registration.example global/xxx.yyy
,
Indeed I miswrote that in the original issue, it's fixed!
Community Note
Terraform Version & Provider Version(s)
Terraform v1.8.3 on linux_amd64
Affected Resource(s)
google_clouddomains_registration
Terraform Configuration
Debug Output
No response
Expected Behavior
When I import an existing resource
terraform import google_clouddomains_registration.example global/xxx.yyy
with a configuration copy/pasted directly from the GCP console, I can apply my configuration without aforces replacement
.yearly_price
should absolutely not be a required argument, but rather an attribute.Actual Behavior
No response
Steps to reproduce
terraform import google_clouddomains_registration.example global/xxx.yyy
terraform plan -target google_clouddomains_registration.example
Important Factoids
No response
References
No response