Unsuitable value for child module variable "backends" about terraform-google-lb-http HOT 8 CLOSED

Unfortunately Terraform Core doesn't support optional object values - hashicorp/terraform#19898

from terraform-google-lb-http.

Can confirm I have the same issue.

from terraform-google-lb-http.

@nguyen-doan I had same problem when only google provider was used. After added google-beta provider, error was gone.

from terraform-google-lb-http.

I have the same issue even with the google-beta provider 🤷

from terraform-google-lb-http.

Currently the module expects full backend declarations without using the defaults for the "backends" definition. I think it used to be better in the past, where only some of the params were required.

from terraform-google-lb-http.

That's indeed sad, having hashicorp/terraform#22449 would be a step forward.
Just out of curiosity, why was it possible in the past? I can see the configuration data format was different back then, but I'm just wondering if some mix of past approach with current configuration scheme would be possible to achieve..

from terraform-google-lb-http.

Please check here, apparently we can set type=any but we lose variable validation until version 0.13 using validate blocks.

from terraform-google-lb-http.

If anyone else hits this, I side-stepped the issue on an old project by editing .terraform/modules/gce-lb-http/variables.tf to change the backend to type=any long enough to upgrade to Terraform 0.13, running an apply (which produced no changes) to bump the saved state version, and then upgrading to Terraform 0.14, which has better validation which reports the specific failing element.

In my project these backend additions were required to match the existing config:

custom_request_headers = null
security_policy        = null
iap_config = {
  enable = false
  enable               = false
  oauth2_client_id     = null
  oauth2_client_secret = null
}

… and the health-check required adding logging = null

from terraform-google-lb-http.