-
Notifications
You must be signed in to change notification settings - Fork 630
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
Wrong account_id using cloudflare_accounts Data Source #1956
Comments
Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of This issue has been marked with |
here there is the output requested
The value got for account_id is wrong. I've seen this Shall I escape them somehow? I had to use
Through curl I'm doing a request to same endpoint but using HTTP/2
I also tried the data source with this but I'm still getting wrong account_id
|
the functionality here is working correctly for me. i think the issue is that you're referencing the resource ID, not the account ID ( the difference is mentioned on the docs page for the two fields and their intentions. |
You're right! Thank you for your support on this |
Confirmation
Terraform and Cloudflare provider version
Affected resource(s)
cloudflare_accounts (Data Source)
I've used a local variable to set the CloudFlare account id. Now trying to use this data source https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/data-sources/accounts
I'm getting an unexpected value.
I'm able to resolve and get the properly account ID through this API call
I'm using a account name like this "Company - Testing" Maybe some character is not correctly parsed from the provider?
Terraform configuration files
Link to debug output
nothing relevant to add here
Panic output
No response
Expected output
Actual output
Steps to reproduce
Additional factoids
No response
References
#1902
https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/data-sources/accounts
The text was updated successfully, but these errors were encountered: