feat: updates to fix Region name now being appended to azFw policy name #914 #915
+283
−168
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces several changes to the
infra-as-code/bicep/modules/vwanConnectivity
module, primarily focusing on the addition of new parameters and the restructuring of resource definitions to support different deployment styles for Azure Firewall policies. The most important changes include the introduction of theparAzFirewallPolicyDeploymentStyle
parameter, the addition of custom names for Azure Firewall policies viaparAzFirewallPolicyCustomName
, and the refactoring of resource definitions to support both shared global and per-region deployment styles.Why
This was needed to fix #914, but it also posed the question of how customers should deploy the Azure Firewall Policy in a multi region configuration, today the module would create a policy per region, but that may not be desired. Hence the module now supports, via this PR, the ability to chose between a
PerRegion
orSharedGlobal
firewall policy deployment approach.New Parameters and Types:
parAzFirewallPolicyDeploymentStyle
parameter to specify the deployment style of Azure Firewall policies (SharedGlobal
orPerRegion
). [1] [2] [3] [4]azFirewallPolicyDeploymentStyleType
type to define the possible values forparAzFirewallPolicyDeploymentStyle
.Custom Names for Policies:
parAzFirewallPolicyCustomName
parameter to allow specifying custom names for Azure Firewall policies.Resource Definitions Refactoring:
resVhub
,resVhubLock
,resVhubRouteTable
,resVhubRoutingIntent
,resVpnGateway
,resVpnGatewayLock
,resErGateway
, andresErGatewayLock
resources to use a more consistent and readable array syntax. [1] [2] [3] [4] [5]Output Adjustments:
Testing Evidence
vwanConnectivity.bicep - defaults with VPN, DDOS & EX disabled (for speed)
vwanConnectivity.bicep - Multi Region Param with VPN, DDOS & EX disabled (for speed) - one hub with custom FW policy name