Breaking change
Despite the language in #42, which was closed by PR #86 which introduced existing_nat_ips, and the description of the existing_nat_ips variable, the previous behavior was that if you provide existing IPs, they are assumed to be connected to existing NAT gateways or instances. No new gateways are created. "existing_nat_ips" is interpreted to mean the IPs of existing NATs.
That behavior makes no sense. Nothing was done with the existing IPs, all that happened if you provided them was that no NATs were created. The same effect could be achieved by setting both nat_gateway_enabled and nat_instance_enabled to false.
This release renames existing_nat_ips to nat_elastic_ips, so that anyone using existing_nat_ips will be notified about the change in behavior, which otherwise could go unnoticed and be expensive. To retain the old behavior, set nat_elastic_ips to the same list you previously used to set existing_nat_ips, and set both nat_gateway_enabled and nat_instance_enabled to false.
The new behavior is that creation of NAT gateways and/or instances is controlled only by nat_gateway_enabled and nat_instance_enabled. If you supply nat_elastic_ips, you must supply at least enough IPs for all the created gateways/instances, and the provided IPs will be assigned to them. Otherwise, this module will allocate new elastic IPs for them.
remove check for existing ips on local.nat_gateways_count @joe-niland (#109)
what
why
references