Skip to content

[v3.1.0] Private DNS, virtual hub and Azure Monitor updates
Compare
Choose a tag to compare
@krowlandson krowlandson released this 23 Dec 20:27
· 140 commits to main since this release
v3.1.0
86f630a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Overview

The v3.1.0 release includes a number of updates as listed below. These focus primarily on private DNS zones for private endpoints, virtual hub, and Azure Monitor.

New features

  • Added privatelink.kubernetesconfiguration.azure.com to list of private DNS zones for azure_arc private endpoints
  • Added option to enable private DNS zone privatelink.blob.core.windows.net for Azure Managed Disks
  • Added option to enable internet_security_enabled on azurerm_virtual_hub_connection resources for secure virtual hubs
  • Added option to specify a list of virtual networks for linking to private DNS zones without association to a hub
  • Added advanced option to specify existing resource group (by name) for Virtual WAN resources1
  • Added Wiki documentation and a working example showing how to segregate deployment of an Azure landing zone across multiple module instances for connectivity, management and core resources
  • Added Wiki documentation for the custom_policy_roles input variable
  • Added Wiki documentation for video guides relating to the module
  • Added new settings for azurerm_log_analytics_workspace and azurerm_automation_account resources (via advanced input)
  • Updated Deploy-Diagnostics-LogAnalytics policy set definition to use the latest built-in policy definitions for Azure Storage
  • Updated parameters for the Deploy-ASC-Monitoring Policy Assignment
  • Updated managed parameters set for the Deploy-Private-DNS-Zones Policy Assignment
  • Updated logic for DNS zone virtual network links to prevent disabled hubs from being included
  • Updated logic for hub virtual network mesh peering to prevent disabled hubs from being included
  • Updated default values for optional() connectivity inputs
  • Updated Wiki documentation to add new content to the FAQ page
  • Removed the deprecated ActivityLog Azure Monitor solution
  • Removed sensitive value filtering for Log Analytics workspace resources
  • Removed location from azureBatchPrivateDnsZoneId parameter for Deploy-Private-DNS-Zones policy assignment

Fixed issues

  • Fix #482 (Review and update private DNS zones for private endpoint #482)
  • Fix #491 (Feature Request - vwan hub connections - Internet_Security_Enabled should be a variable. #491)
  • Fix #492 (Feature Request - configure automation account in management subscription #492)
  • Fix #528 (Validate parameters for Azure Security Benchmark in TF deployment #528)
  • Fix #542 (Bug Report - enable_private_dns_zone_virtual_network_link_on_hubs = true failing on disabled hub #542)
  • Fix #549 (Feature Request: Deploy private dns zones and link them to an existing vnet #549)
  • Fix #552 (Feature Request: Multiple Hub scenario, 2 VWANS are getting deployed #552)
  • Fix #553 (Remove Activity Log solution from Terraform RI #553)
  • Fix #544 (Missing assignment parameter values for "Configure Azure PaaS services to use private DNS zones" #544)
  • Fix #556 (Unexpected behaviour: Radius IP required when using AAD for VPN gateway #556)
  • Close #176 (Create Wiki docs page - [Variables] custom_policy_roles #176)
  • Close #378 (Feature Request - Pricing/costing estimates #378)
  • Close #392 (Add documentation for deploying across multiple Terraform workspaces (Terraform state file segregation) #392)
  • Close #499 (Bug Report Terraform plan fails due to sensitive values in azurerm_automation_account output #499)
  • Close #567 (Feature Request - Videos to Assist Written Documentation #567)

Breaking changes

n/a

Input variable changes

The following non-breaking changes have been made to the input variables. Although these don't need to be changed for the module to work, please review to prevent unwanted resource changes and to remove code that is no-longer required.

  • Added configure_connectivity_resources.settings.dns.config.enable_private_link_by_service.azure_managed_disks
  • Added configure_connectivity_resources.settings.dns.config.virtual_network_resource_ids_to_link
  • Added configure_connectivity_resources.settings.vwan_hub_networks.*.config.secure_spoke_virtual_network_resource_ids
  • Added configure_connectivity_resources.advanced.existing_virtual_wan_resource_group_name
  • Removed configure_management_resources.settings.log_analytics.config.enable_solution_for_azure_activity

For more information

Full Changelog: v3.0.0...v3.1.0

  1. The ability to specify an existing resource group (by name) for Virtual WAN resources is to satisfy the preference of some customers to place all Virtual WAN resources in a single resource group, consistent with the Portal experience where this is a limitation. ↩

Assets 2
Loading