Skip to content
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

cloudflare_web_analytics_site error 10000 #3234

Closed
2 tasks done
jean-mercier-hivebrite opened this issue Apr 8, 2024 · 4 comments
Closed
2 tasks done

cloudflare_web_analytics_site error 10000 #3234

jean-mercier-hivebrite opened this issue Apr 8, 2024 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@jean-mercier-hivebrite
Copy link

Confirmation

  • My issue isn't already found on the issue tracker.
  • I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

cloudflare = {
  source  = "cloudflare/cloudflare"
  version = "4.29.0"
}

terraform 1.7.2

Affected resource(s)

cloudflare_web_analytics_site

Terraform configuration files

resource "cloudflare_web_analytics_site" "web_analytics" {
  account_id   = local.account_id
  zone_tag     = module.cloudflare.cloudflare_zones_id
  auto_install = true
}

Link to debug output

sensitive

Panic output

No response

Expected output

Ressource should be created and provider should be able to call it to get information

Actual output

│ Error: error getting web analytics site "XXXXXXXXXX": Authentication error (10000)

│ with cloudflare_web_analytics_site.web_analytics,
│ on webanalytics.tf line 2, in resource "cloudflare_web_analytics_site" "web_analytics":
│ 2: resource "cloudflare_web_analytics_site" "web_analytics" {

Steps to reproduce

terraform apply

the creation is done but the apply end with this error

also after all the plan fail with this error

Additional factoids

My token have all the permission available through the cloudflare UI

References

No response

@jean-mercier-hivebrite jean-mercier-hivebrite added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 8, 2024
Copy link
Contributor

github-actions bot commented Apr 8, 2024

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

Copy link
Contributor

github-actions bot commented Apr 8, 2024

Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of TF_LOG=DEBUG output to be provided. The only parts that should be redacted are your user credentials in the X-Auth-Key, X-Auth-Email and Authorization HTTP headers. Details such as zone or account identifiers are not considered sensitive but can be redacted if you are very cautious. This log file provides additional context from Terraform, the provider and the Cloudflare API that helps in debugging issues. Without it, maintainers are very limited in what they can do and may hamper diagnosis efforts.

This issue has been marked with triage/needs-information and is unlikely to receive maintainer attention until the log file is provided making this a complete bug report.

@github-actions github-actions bot added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 8, 2024
Copy link
Contributor

github-actions bot commented May 9, 2024

Marking this issue as stale due to 30 days of inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed. Maintainers can also remove the lifecycle/stale label.
If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

Copy link
Contributor

This issue was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

1 participant