Open martysweet opened 1 hour ago
Voting for Prioritization
Volunteering to Work on This Issue
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.
I can't provide the full log as there is considerable sensitive information throughout. As this is a 500 error, there should be server-side logs to highlight the issue.
Confirmation
Terraform and Cloudflare provider version
terraform-provider-cloudflare/4.44.0 terraform-plugin-sdk/2.34.0 terraform/1.5.7
4.45.0 doesn't appear to be available for ARM, but changelog does not indicate changes would resolve issues.
Affected resource(s)
cloudflare_zero_trust_access_application cloudflare_access_application
Terraform configuration files
Link to debug output
https://gist.github.com/martysweet/5d6cc8a0569bc8b14d9fdff2d05b4442
Panic output
No response
Expected output
Actual output
Error: error creating Access Application for accounts "xyz": error from makeRequest: received internal server error response (HTTP 500), please try again later
Steps to reproduce
Additional factoids
The API called https://developers.cloudflare.com/api/operations/access-applications-add-an-application Shows policies should be an array of {id, precedence}, however, the Terraform provider is sending an array of policy IDs.
Commenting out policies results in the successful creation of the resource, so I believe this is the issue, likely with a change with the backend API.
Current workaround is to create in the UI and import the application and policy.
References
No response