User for the Cloud Failover Extension (CFE) use case wants to deploy two BIG-IP instances, but only have one of the instances get created with an associated public IP address for the secondary IP...the VIP. Why? CFE will only map one public IP to the private IP listener address.
The current bigip module has an option for public_ip but that applies to all interfaces and their public IPs. What I want is a new parameter flag associated with something like "create secondary VIP public IP" or suggested by F5 PD would be "cfe_secondary_vip_disable" new parameter. If true, then the BIG-IP creates public IPs for mgmt and external primary IP but NOT for the external secondary IP on the NIC.
User for the Cloud Failover Extension (CFE) use case wants to deploy two BIG-IP instances, but only have one of the instances get created with an associated public IP address for the secondary IP...the VIP. Why? CFE will only map one public IP to the private IP listener address.
The current bigip module has an option for public_ip but that applies to all interfaces and their public IPs. What I want is a new parameter flag associated with something like "create secondary VIP public IP" or suggested by F5 PD would be "cfe_secondary_vip_disable" new parameter. If true, then the BIG-IP creates public IPs for mgmt and external primary IP but NOT for the external secondary IP on the NIC.
Example...
default value cfe_secondary_vip_disable=false
similar to AWS ticket https://github.com/F5Networks/terraform-aws-bigip-module/issues/38