{FrontDoor}Add --sensitivity parameter to waf-policy managed-rules override add

[Ptnan7]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

⚠️Azure CLI Extensions Breaking Change Test

⚠️front-door

rule	cmd_name	rule_message	suggest_message
⚠️ 1006 - ParaAdd	network front-door waf-policy managed-rules override add	cmd network front-door waf-policy managed-rules override add added parameter sensitivity

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[github-actions]

CodeGen Tools Feedback Collection

Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey

[github-actions]

• For more info about extension versioning, please refer to Extension version schema

[Copilot]

Pull request overview

This PR updates the front-door Azure CLI extension to support configuring managed rule override sensitivity for Front Door WAF policies, primarily to enable DDoS managed rule set override scenarios.

Changes:

• Add --sensitivity to az network front-door waf-policy managed-rules override add and serialize it into the override payload.
• Bump extension version to 2.0.1.
• Document the change in HISTORY.rst.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/front-door/azext_front_door/custom_waf.py	Adds --sensitivity argument and includes it in the managed rule override body.
src/front-door/setup.py	Version bump to 2.0.1.
src/front-door/HISTORY.rst	Adds release note entry for the new --sensitivity parameter.

[Copilot]

New --sensitivity behavior is added here but there’s no test exercising it. Since this extension already has scenario coverage for managed-rules override add (see existing WAF scenario tests), please add/extend a test to call the command with --sensitivity (e.g., High/Medium/Low) and assert the returned override includes the expected sensitivity value so regressions are caught.

[necusjz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[azclibot]

[Release] Update index.json for extension [ front-door-2.1.0 ] : https://dev.azure.com/msazure/One/_build/results?buildId=153376041&view=results