Azure / Azure/bicep-registry-modules

[AVM Module Issue]: front door waf policy creates default geofilter rule that's broken

Open
#6,035 8 comments 0 reactions 1 assignee Claimed by @PaulJohnston88 View on GitHub
Class: Resource Module :package: Needs: Immediate Attention :bangbang: Needs: Triage :mag: Status: Response Overdue :triangular_flag_on_post: Type: AVM :a: :v: :m: Type: Bug :bug:
Dominant language
Bicep
Stars
736
Forks
564
Avg merge
3d 15h
Merged PRs (30d)
30

Description

### Check for previous/existing GitHub issues

- [x] I have checked for previous/existing GitHub issues

### Issue Type?

Bug

### Module Name

avm/res/network/front-door-web-application-firewall-policy

### (Optional) Module Version

0.3.2

### Description

Here's the rule it creates by default

Image

here's the code from the module:

```bicep
@description('Optional. The custom rules inside the policy.')
param customRules customRulesType = {
rules: [
{
name: 'ApplyGeoFilter'
priority: 100
enabledState: 'Enabled'
ruleType: 'MatchRule'
action: 'Block'
matchConditions: [
{
matchVariable: 'RemoteAddr'
operator: 'GeoMatch'
negateCondition: true
matchValue: ['ZZ']
}
]
}
]
}
```
don't see it in the repo though

### (Optional) Correlation Id

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.