-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Failed to create CloudFlare Record: API Error: Zone does not exist. #2551
Comments
I'm subscribing here as well - the upstream API used for CloudFlare (pearkes/cloudflare) prohibits Terraform from supporting the other APIs that CloudFlare exposes, like page rules (which would be the exact kind of thing that you'd want to manage with Terraform). |
Would be great to update |
This is an issue for us as well |
Hi all The cloudflare provider now uses the official cloudflare API - please can you tell me if this is still an error? Thanks Paul |
This is still an issue in Terraform 0.7.0, I believe it's the same issue. I get:
|
Hey @stack72 not sure if you've seen this - worth removing the "waiting-response" label? |
@stack72 i guess i am getting same error in Terraform v0.7.7 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
In a CloudFlare multi-user organizational account no single user owns the data, but only has access rights to it, while it's owned by the organization. This causes zones seemingly not to exist when you try to add a record using one of the users and their api key.
The old api (https://www.cloudflare.com/docs/client-api.html) does not support the multi-user model, where the new one (https://api.cloudflare.com/) does.
I see the https://github.com/pearkes/cloudflare/ provider still uses the old api. Should I raise this issue with pearkes?
The text was updated successfully, but these errors were encountered: