Az.Network: Typo NegateConditon instead of NegateCondition

Open Beginner friendly
#12,500 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
64/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp, powershell
Domain
cli

Research direction

Start with the Az.Network implementation and the New-AzApplicationGatewayFirewallCondition entry point, then compare its parameter name with the linked Azure WAF documentation. Confirm the corrected NegateCondition spelling is used consistently and verify the module behavior or relevant checks for Az.Network 3.2.0 compatibility.

Written by the indexing model from the issue text.

Description

act-quality-productivity-squad customer-reported Network - Application Gateway question Service Attention

Description

Azure documentation says that PowerShell commandlet New-AzApplicationGatewayFirewallCondition has a parameter -NegateCondition, however this is currently wrong since there is a typo in the code and there is NegateConditon instead (notice the missing i).

Documentation:
https://docs.microsoft.com/en-us/azure/web-application-firewall/ag/configure-waf-custom-rules

Code:
image

Module versions

Az.Network 3.2.0

Dominant language
C#
Stars
4.8k
Forks
4.3k
Avg merge
3d 21h
Merged PRs (30d)
49

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/azure-powershell

All issues in Azure/azure-powershell

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.