You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added a new property to the subnet input variable map, no_addr_prefix, that if set to "true" will not automatically create a new matching address prefix for the subnet, no matter the condition. (#741) (cad676e)
moved the management-vpc and workload-vpc submodule from the submodules directory to the modules directory to confirm with Hashicorp practises. See updated usage blocks on how to consume. (#694) (f583bbb)
added new input variables to give full flexibility over VPC resource naming. New variables include: vpc_flow_logs_name, public_gateway_name, routing_table_name, dns_custom_resolver_name, dns_instance_name, and dns_binding_name. (#697) (760689b)
Resolve the issue where the VPC stack continues to auto-generate address prefixes, despite having subnet address prefixes explicitly passed to the module. (#679) (e3640c6)
IMPORTANT NOTE:
If you are using the module in a previous version, and passing only subnets as inputs with address_prefixes set to null or not set, upgrading to this version may cause the VPC to be deleted and recreated because the VPC configuration will change from address_prefix_management being set to "auto" to being set to "manual": ~ address_prefix_management = "auto" -> "manual" # forces replacement .