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_zone data source doesn't include verification_key for partial zones. #3252

Closed
2 tasks done
averagepyro opened this issue Apr 17, 2024 · 5 comments
Closed
2 tasks done
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

@averagepyro
Copy link

averagepyro commented Apr 17, 2024

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

Terraform 1.7.1
Cloudflare 4.30.0

Affected resource(s)

cloudflare_zone data source

Terraform configuration files

data cloudflare_zone "zone" {
    account_id = var.account_id
    zone_id = var.zone_id
}

output "output" {
  value = {
    verification_key : data.cloudflare_zone.zone.verification_key
  }
}

Link to debug output

https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/data-sources/zone

Panic output

N/A

Expected output

I would like this to return the partial zone's verification key to this output.

Actual output

Error: Unsupported attribute on outputs.tf line 4, in output "output": 4: verification_key : data.cloudflare_zone.zone.verification_key

This object has no argument, nested block, or exported attribute named "verification_key".

Steps to reproduce

  1. Use the terraform example above and run terraform plan

Additional factoids

We have a group of super admins that are allowed to use terraform to create zones. In a separate repo, other admins are able to use terraform to manage those zones. It would be very handy to use this data source to pass the verification key without requring our super admins to copy/paste and send to the operation admin group.

The cloudflare_zone resource does provide the verification key, but it is missing from the data source.

References

No response

@averagepyro averagepyro 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 17, 2024
Copy link
Contributor

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

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 17, 2024
@averagepyro
Copy link
Author

Copy link
Contributor

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 26, 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