-
Notifications
You must be signed in to change notification settings - Fork 637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Destroy errors out on read-only resources #531
Comments
What I suspect is happening here is that the zone is created but it hasn't been converted to an Enterprise zone when the resource is destroyed, it still doesn't have access to it. I don't think we can do anything in the provider at this stage to cleanly account for this. If the above is indeed what is happening, the advice I have been giving to people is to do it in two steps. Create the zone and get it setup as an Enterprise zone in your account and then try to applying changes to it. Also, if you're not using those settings, just omit them to leave them as the defaults. |
#599 is mentioned to have addressed this. @inge4pres would you mind checking out master and confirming this is the case for you? |
Closing this off as #599 mentions a potential fix. Can reopen if we needed to explore further. |
Not convinced this has been fixed. Following error when trying to destroy customer settings. terraform-provider-cloudflare_v2.7.0_x4 |
Hello,
this is a report of an error occurred during the destroy phase for a zone.
We're testing migration to v2 provider by creating/destroying a test zone.
Terraform Version
terraform 0.11.14
terraform-provider-cloudflare 2.0.1
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Expected Behavior
No error in destroying the resources
Actual Behavior
This error shows up:
Looks like the destroy cycle tries to set an attribute to the zone before destroying...
Steps to Reproduce
terraform apply
terraform destroy
The text was updated successfully, but these errors were encountered: