2.0 GCP terraform provider new install - invalid or unknown key: labels

[phatwila]

The latest GCP terraform provider 2.0 does not support labels, causing new installs to fail.

[root@terraform-node dcos-tf-gcp-demo]# terraform plan -out=plan.out
Error: module.dcos.module.dcos-infrastructure.module.dcos-forwarding-rules.module.dcos-forwarding-rule-masters.module.dcos-forwarding-rule-masters.google_compute_forwarding_rule.forwarding_rule_config[0]: : invalid or unknown key: labels

Error: module.dcos.module.dcos-infrastructure.module.dcos-forwarding-rules.module.dcos-forwarding-rule-masters.module.dcos-forwarding-rule-masters.google_compute_forwarding_rule.forwarding_rule_config[1]: : invalid or unknown key: labels

Error: module.dcos.module.dcos-infrastructure.module.dcos-forwarding-rules.module.dcos-forwarding-rule-public-agents.module.dcos-forwarding-rule-public-agents.google_compute_forwarding_rule.forwarding_rule_config: : invalid or unknown key: labels

From the slack channel a temporary work-around is to force the 1.18.0 provider version in main.tf:

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

module "dcos" {
  [...]

  providers = {
    google = "google"
  }  
}

[bernadinm]

This is resolved by d2iq-archive/dcos-docs-site#2023

[rolyv]

Has the mesosphere team considered just using the "google-beta" provider instead? I see in other issue threads that you're saying "labels was deprecated". It wasn't deprecated, it was just moved to the "google-beta" terraform provider. So there is another choice on the table of switching your terraform modules to use that provider instead. Have you guys considered that? @bernadinm