bbl up fails on Azure (public IPs not available)

[zmb3]

I downloaded the v6.0 binary from the releases page and tried to do a bbl plan + bbl up on Azure. The bbl up step fails with the following errors:

Error: Error applying plan:

3 error(s) occurred:

* output.external_ip: Resource 'azurerm_public_ip.bosh' does not have attribute 'ip_address' for variable 'azurerm_public_ip.bosh.ip_address'
* output.jumpbox_url: Resource 'azurerm_public_ip.bosh' does not have attribute 'ip_address' for variable 'azurerm_public_ip.bosh.ip_address'
* output.director_address: Resource 'azurerm_public_ip.bosh' does not have attribute 'ip_address' for variable 'azurerm_public_ip.bosh.ip_address'

I tore everything down, went back to v5.11.5, re-planned, and got the same result. It seems this may be related to hashicorp/terraform-provider-azurerm#310.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/154708010

The labels on this github issue will be updated when the story is started.

[genevieve]

We haven't seen that issue locally. I'll try to reproduce and potentially add their depends_upon workaround!

[genevieve]

That issue seems to be releated to dynamically allocated IPs. We chose static allocation so the resource should be available at the time that the outputs are printed during terraform apply. We can try creating the data source for it and then the output can depend on it.

[genevieve]

I reverted to terraform azure provider v1.0.0 and got a bbl environment. This might be tied to the latest release of the provider v1.1.0 from 3 days ago.

[zmb3]

I’ll check which version I was running locally as soon as I get to the office. We’re you able to reproduce with 1.1.0 then?

[genevieve]

Yes, reproduced.

[genevieve]

Made a PR to the azure provider here: hashicorp/terraform-provider-azurerm#772

[genevieve]

We pinned the provider temporarily and this will be out in the next release of bbl!