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

provider docs: resource cloudflare_api_token uses removed data.cloudflare_api_token_permission_groups in example #4171

Closed
tom-futo opened this issue Oct 2, 2024 · 4 comments
Labels
kind/support Categorizes issue or PR as related to user support. working-as-intended Indicates an issue is working as designed.

Comments

@tom-futo
Copy link

tom-futo commented Oct 2, 2024

data source cloudflare_api_token_permission_groups removed, referenced elsewhere in provider docs

Affected resource(s)

api_token
maybe others

@tom-futo tom-futo 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 Oct 2, 2024
Copy link
Contributor

github-actions bot commented Oct 2, 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 Oct 2, 2024
Copy link
Contributor

github-actions bot commented Oct 2, 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.

@tom-futo
Copy link
Author

tom-futo commented Oct 2, 2024

Might be worth adding a simpler issue template for minor doc things like this

@jacobbednarz
Copy link
Member

you're viewing the v5 docs which are in alpha and not complete - this is still present in 4.x. 5.x documentation changes will be made at a later date.

@jacobbednarz jacobbednarz closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2024
@jacobbednarz jacobbednarz added kind/support Categorizes issue or PR as related to user support. working-as-intended Indicates an issue is working as designed. and removed kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it. labels Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as related to user support. working-as-intended Indicates an issue is working as designed.
Projects
None yet
Development

No branches or pull requests

2 participants