terraform fails when bigip is not ready

[yossi-r]

i'm using terraform to deploy a bigip in AWS using, then i want to use the bigip provider to configure the bigip. the error i'm getting is: Error: BigIP provider requires address, username and password

the problem (as i understand it) is that when terraform apply, it starts with terraform plan which triggers the bigip provider (for a bigip that doesn't exist yet). for this use case we need the provider to be more relaxed regarding the inputs.

Thanks

[RavinderReddyF5]

@yossi-r Can you please share the terraform config you are using?

[amolari]

@RavinderReddyF5 Got the same. Found this: https://github.com/hashicorp/terraform/issues/2430. Maybe a Terraform issue. I haven't found a workaround (except run terraform twice, once for the aws resources creation, then for the bigip resources).

[rabru]

I got the same issue as well. Can you please fix it, since it is quite common do deploy the VM and do the DO directly in the same deployment. I use it in GCP:

provider "bigip" {
  address = "${google_compute_instance.bigip.network_interface.0.access_config.0.nat_ip}:8443"
  username = var.uname
  password = var.upassword
}

resource "bigip_do"  "bigip-a" {
     do_json = data.template_file.DO_json.rendered
     tenant_name = "sample_test1"
 }

[focrensh]

The issue @amolari mentioned above does follow this same pattern. In summary, it's providers being dependent on objects from other providers. There is no "depends_on" logic built into the providers themselves.

Investigating with TF-115