Bug: Deprecated Terraform Resource attribute for IBM Cloud Virtual Servers
sean-freeman opened this issue · comments
Version
All
Platform:
ibmcloud
Install types impacted:
- ☑️ IPI (automated install with
openshift-install) - ☑️ UPI (semi-manual installation on customised infrastructure)
What happened?
Errors during runtime:
DEBUG ibm_is_lb_pool_member.machine_config: Creation complete after 3m26s [id=]
DEBUG
DEBUG Warning: Deprecated attribute
DEBUG
DEBUG on main.tf line 118, in resource "ibm_is_lb_pool_member" "kubernetes_api_public":
DEBUG 118: target_address = ibm_is_instance.bootstrap_node.primary_network_interface.0.primary_ipv4_address
DEBUG
DEBUG The attribute "primary_ipv4_address" is deprecated. Refer to the provider
DEBUG documentation for details.
DEBUG
DEBUG (and 11 more similar warnings elsewhere)
DEBUG
DEBUG Apply complete! Resources: 12 added, 0 changed, 0 destroyed.What you expected to happen?
No error, deprecation occured in the Terraform Provider a long while ago.
How to reproduce it (as minimally and precisely as possible)?
Any of the following code executed during normal runtime:
https://github.com/search?q=repo%3Aopenshift%2Finstaller%20primary_ipv4_address&type=code
Anything else we need to know?
Replacement code is simple:
Before:
ibm_is_instance.example.primary_network_interface.0.primary_ipv4_address
ibm_is_instance.example.primary_network_interface[0].primary_ipv4_address
After:
ibm_is_instance.example.primary_network_interface.0.primary_ip.0.address
ibm_is_instance.example.primary_network_interface[0].primary_ip[0].address
References
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale