Relax version constraints about terraform-google-lb-http HOT 4 CLOSED

I've hit this issue to: I need to use newer version of the google-beta provider which supports IAM Conditions. Unfortunately, I can't do that because of the constraints in the module.

The official recommendation for modules is to use >=

Specifying Required Provider Versions

Re-usable modules should constrain only the minimum allowed version, such as >= 1.0.0. This specifies the earliest version that the module is compatible with while leaving the user of the module flexibility to upgrade to newer versions of the provider without altering the module.

from terraform-google-lb-http.

We intentionally pin our versions pessmistically to prevent unexpected errors, but I would be happy to review/accept a PR which changes the version constraint to >= 2.15, <4.0 and updates the version used in tests.

from terraform-google-lb-http.

@morgante @Dev25 I think you missed one of the version constraints...
In test/setup/versions.tf I can still see the following block:

provider "google" {
  version = "~> 2.15"
}

provider "google-beta" {
  version = "~> 2.15"
}

This causes terraform init to fail with this error:

Error: provider.google-beta: no suitable version installed
  version requirements: "~> 2.15,~> 2.15"
  versions installed: "3.6.0"

Error: provider.google: no suitable version installed
  version requirements: "~> 2.15,~> 2.15"
  versions installed: "3.6.0"

from terraform-google-lb-http.

I think this issue should be re-opened

from terraform-google-lb-http.