Azure/terraform-azurerm-caf-enterprise-scale v2.4.0

Update subnet creation logic and add linked automation account region mapping

on GitHub

What's Changed

This release contains a number of changes relating to the functionality of this module.

• Updated logic controlling whether to create GatewaySubnet and AzureFirewallSubnet subnets to fix #450
• Added new logic to automatically map the supported location for linked Automation Accounts when deploying to East US or East US 2 regions to fix #449
• Replaced more try() functions with lookup() as part of working towards #227
• Updated custom policies to include new ALZ-specific metadata
• Updated the deployment names in Deploy-VNET-HubSpoke policy definition

Breaking changes

• The fix for #450 may result in previously created subnets being removed. This will only be an issue if you have deployed resources into these subnets outside of this module. To ensure these subnets are created without creating any additional new resources, please use the subnets entry to add these back into your configuration as needed.

• The fix for #449 may result in the module wanting to re-create the Automation Account in the "correct" new region. This is only needed if you want to use any of Update Management, Change Tracking or Inventory solutions in Azure Monitor. If you are happy to continue using the previous region, you can override this change by adding the following configuration in the configure_connectivity_resources input variable:

  configure_management_settings= {
    # other settings removed for brevity
    advanced = {
      custom_settings_by_resource_type = {
        azurerm_automation_account = {
          management = {
            location = "eastus"
          }
        }
      }
    }
  }

Full Changelog: v2.3.1...v2.4.0