Terraform-provider-google: Setting quic_override in google_compute_target_https_proxy once stops being optional

Created on 29 Sep 2019  ·  3Comments  ·  Source: hashicorp/terraform-provider-google


Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
  • If an issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.

Terraform Version

Terraform v0.12.9

  • provider.google v2.15.0
  • provider.google-beta v2.15.0

Affected Resource(s)

  • google_compute_target_https_proxy

Terraform Configuration Files

resource "google_compute_target_https_proxy" "test" {
  name             = "tf-test-proxy"
  url_map          = "${google_compute_url_map.test.self_link}"
  ssl_certificates = "${concat([var.test_certificate_link])}"
  #quic_override    = "ENABLE"
}

Debug Output

Panic Output

Error: Error updating TargetHttpsProxy "tf-test-proxy": googleapi: Error 400: Required field 'quicOverride' not specified, required

Expected Behavior


Based on the documentation, the argument is 'optional'. Meaning that setting it once and removing it later shouldn't yield an Error and should set it as default "NONE" as expressed in the documentation.

Actual Behavior

Steps to Reproduce

  1. Create a google_compute_target_https_proxy resource setting the quic_override.
  2. Update the resource description and comment out quic_override.
  1. terraform apply

Important Factoids

References

  • #0000
bug

All 3 comments

Well, that's certainly what it says in the public REST documentation...

image

This is a bug in GCP, then. We'll work around it by explicitly setting the field default to NONE.

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

Was this page helpful?
0 / 5 - 0 ratings