Thank you @Sevenlive for the PR.
Added support for enable_bgp_over_lan and bgp_lan_interfaces_count attributes.
This feature allows you to create a VPC with additional subnets. The primary use case is to allow you to build global spoke VPC's with subnets in multiple regions, without having to resort to native GCP resources.
Previously, subnets in GCP were always named the same as the VPC. Since global VPC allows you to deploy in multiple regions, it seems more apptly to follow the gateway name for naming the subnet. Subnet names are now set using the optional gw_name variable. If you're not using this variable, they will remain using the VPC naming.
│ Error: Invalid function argument │ │ on .terraform/modules/spoke_1/locals.tf line 82, in locals: │ 82: aws = var.use_existing_vpc ? [] : slice(aviatrix_vpc.default[0].public_subnets.*.cidr, 2, length(aviatrix_vpc.default[0].public_subnets)), #Get the rest of the public subnets, minus the first 2.
Enabled by default and enhances gateway performance. This setting can be used to turn it off.
New supported arguments for this feature:
- allocate_new_eip
- eip
- ha_eip
- azure_eip_name_resource_group
- ha_azure_eip_name_resource_group
- additional_group_mode_eips
- additional_group_mode_azure_eip_name_resource_groups
For beter readability, the locals are no longer part of variables.tf and can now be found in locals.tf.
This feature allows for more than 2 spoke gateways to be deployed in a spoke. For details on migrating from traditional to group mode, check this doc.
New supported arguments for this feature:
- additional_group_mode_subnets
- additional_group_mode_azs
- group_mode
- spoke_gw_amount
- manage_ha_gateway
This release is purely providing compatibility with these versions. New features that are part of the 7.0.0/3.0.0 release will be part of subsequent releases.
Switch from gw_name to id attribute for resources referring to the spoke gateway. This provides better lifecycle handling.
This version was pulled because of a bug
Issue#8 - Fix network segmentation on GW recreation
In scenario's where the spoke gateway needs to be recreated (e.g. moving from non-HPE to HPE), the new gateway would not be reattached to the network domain. Switching from gw_name to id as reference resolves this.
Issue#10 - Improve lifecycle handing
In certain scenario's spoke attachment and network domain association need to be recreated. This is handled with the replace_triggered_by argument added in Terraform 1.2.0.
These arguments were added to support this:
- private_mode_subnets
- private_mode_lb_vpc_id
- private_mode_subnet_zone
- ha_private_mode_subnet_zone
- enable_max_performance
- spoke_prepend_as_path
- transit_prepend_as_path
By default this module will use the name argument for both VPC/VNET creation as well as spoke gateway. You can now override the gateway name with the gw_name argument.
Most input variables that have a default value, have been set to be non-nullable as of this release. This allows parent or root modules calling this module to set arguments to null without changing the internal behavior of the module. This should cause no impact to existing usage.
As availability zones are not supported in the Aviatrix controller for Gov and DoD regions, the module automatically selects az_support = false, for these regions.
In previous versions, the wrong subnet was selected for deploying the spoke gateway(s).
Controller does not allow for names longer than 30 characters for VPC's, VNET'sand VCN's. As of this version, any names longer than that are automatically truncated.
New variables available for configuration:
availability_domain
ha_availability_domain
fault_domain
ha_fault_domain
Previously, the module assumed multiple AD's available in every region. As per this release, it can handle single AD regions as well.
As per this note, in 6.7 and provider version 2.22.0, the aviatrix_segmentation_security_domain_association resource has been renamed to aviatrix_segmentation_network_domain_association. Follow the guidance in the note to migrate to this module version. Failure to do so, may result in downtime, as upgrading to this module version will force the existing aviatrix_segmentation_security_domain_association to be removed while the aviatrix_segmentation_network_domain_association may not yet be in place.
This option allows you to increase the receive buffer size. This may be required in scenarios where traffic is particularly bursty.
aviatrix_spoke_transit_attachment was changed to use spoke ID in stead of name, allowing for better dependency handling. Updating spoke where it will be replaced, will now cause the spoke-transit-attachment resource to also be destroyed.
Previously regex mismatched the regions, resulting in the wrong cloud type.
Previously, smaller than /26 was not supported for gateway subnets in order to maintain support for insane mode. Now it can be set to smaller values, if insane mode is disabled.