google_compute_health_check "only one of" error about terraform-google-lb-http HOT 10 CLOSED

Fortunately it looks like someone already opened the correct issue on the provider. Feel free to follow along there: hashicorp/terraform-provider-google#6295

from terraform-google-lb-http.

@juan-vg Would you mind filing an issue on the provider? It should be fixed there.

from terraform-google-lb-http.

@morgante From my point of view the problem is not the provider, as they have warned about this on their upgrade guide.

Is this module which is not properly working

from terraform-google-lb-http.

I'm quite confident this is a provider bug. The module was working before and continues to generate the correct config. They made a breaking change which caused this to stop working and can only be fixed on their end.

As you can see, we're already dynamically generating the correct config (only one kind at a time). This needs to be fixed on the provider.

from terraform-google-lb-http.

@morgante I've set a fixed provider version (one I've previously used and it was working) and the error is still there. I can understand this can come directly from GCP, but the provider seems to not be the guilty one. I can't understand how a breaking change could affect prior versions already released and proved working.

Moreover, if you're dynamically generating the correct config (btw, "as you can see"? where?), why when I remove a piece of code from this module the error disappears? What I remove is the part where extra health_checks are being generated in this module, so looks like the configuration is not that correct

from terraform-google-lb-http.

Your own bug report state this issue only occurs on the 3.20 provider. It's self-evidently a provider issue.

The reason your workaround work is that you simply entirely removed dynamic blocks which you happen to not be using. We cannot remove those blocks entirely because other people's use case requires them.

The blocks are correctly generated. The issue is the provider is attempting to validate as though all blocks are being set, even though in reality only 1 is generated at a time.

Once again, there is absolutely no action to be taken for the module.

from terraform-google-lb-http.

@morgante My fault then. I've explained myself wrong. It started happening at the same time a new provider has been released.

I've tested this module against provider google-beta versions from 3.18 to 3.20. None work now. Yesterday 3.19 worked as a charm, not today.

Beside the above, there were no code changes from my side. Just stopped working

from terraform-google-lb-http.

There hasn't been any change to this module in 14 days. If your code was working yesterday but not today, it's a provider change.

from terraform-google-lb-http.

@morgante I must apologize. I was setting the version for the google-beta provider. When I did the same for the google one everything started working again. You were completely right.

Sorry for the noise

from terraform-google-lb-http.

No worries, thankfully I think a fix will be available in the next provider release.

from terraform-google-lb-http.