Closed aleksandrovpa closed 2 years ago
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.
Have provided the log file already as attachment since its too big for pasting content
@aleksandrovpa look into Plan-Dependent Settings
I've seen the Unrecognized zone setting name: h2_prioritization
before.
I was able to resolve the issue by setting h2_prioritization = null
which defaults to "off". Unfortunately I see in your config that you're attempting to set h2_prioritization = "on"
so I'm not sure how to resolve the issue.
Have you tried to set h2_prioritization = null
apply the changes and then set h2_prioritization = "on"
and re-apply?
Confirmation
Terraform and Cloudflare provider version
Terraform v1.2.2 on darwin_arm64
Affected resource(s)
cloudflare_zone_settings_override
Terraform configuration files
Debug output
2022-07-15T12:40:59.072+0300 [DEBUG] provider.terraform-provider-cloudflare_v3.18.0: Cloudflare API Response Details: ---[ RESPONSE ]-------------------------------------- HTTP/2.0 400 Bad Request Connection: close Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Cf-Cache-Status: DYNAMIC Cf-Ray: 72b18a213db6152e-LCA Content-Type: application/json Date: Fri, 15 Jul 2022 09:40:59 GMT Expect-Ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" Expires: Sun, 25 Jan 1981 05:00:00 GMT Pragma: no-cache Server: cloudflare Set-Cookie: cflb=0H28vgHxwvgAQtjUGU56Rb8iNWZVUvXho69pAhEykgM; SameSite=Lax; path=/; expires=Fri, 15-Jul-22 12:11:00 GMT; HttpOnly Set-Cookie: cfruid=08df6c05722f05ecea552cf1758d772befb2dec2-1657878059; path=/; domain=.api.cloudflare.com; HttpOnly; Secure; SameSite=None Strict-Transport-Security: max-age=31536000 Vary: Accept-Encoding X-Content-Type-Options: nosniff X-Frame-Options: SAMEORIGIN
{ "success": false, "errors": [ { "code": 1006, "message": "Unrecognized zone setting name: h2_prioritization" } ], "messages": [], "result": null } -----------------------------------------------------: timestamp=2022-07-15T12:40:59.071+0300
log.LOG
Panic output
No response
Expected output
Terraform apply finished without errors
Actual output
Error: Unrecognized zone setting name: h2_prioritization Error: Unrecognized zone setting name: image_resizing
Steps to reproduce
Using cf-terraforming generation create terraform block with existing cloudflare_zone_settings_override, run terraform plan/apply
Additional factoids
I've read all of similar issues here and tried each workaround but have no luck. Also i've turned some parameters to on/off (cause terraform object name is override) but still the same problem. As i can see in API, fields image_resizing and h2_prioritization has a
"editable": true
(also i've tried turn them on/off via UI but have no luck) I've madeterraform state rm
for this resource too.For now, i think we can't use terraform for manage these settings and this is awful. And also very often i get
Error: Plugin did not respond
... We couldn't import it and couldn't create, idk what to say moreReferences
https://github.com/cloudflare/terraform-provider-cloudflare/issues/961 https://github.com/cloudflare/terraform-provider-cloudflare/issues/533 https://github.com/cloudflare/terraform-provider-cloudflare/issues/1297