[FrontDoor] Add WAF ParanoiaLevel, DisplayName and Status to Az.FrontDoor output - #30050
Draft
Shaigoldbourt22 wants to merge 1 commit into
Draft
Conversation
…Door output Bump the Az.FrontDoor swagger pin to API version 2026-04-01 so Get-AzFrontDoorWafManagedRuleSetDefinition returns the new read-only WAF fields: DisplayName and Status on the rule set, and ParanoiaLevel on the rule. The 2026-04-01 spec is additive over 2025-11-01. It adds two definitions (ManagedRuleSetStatus, ParanoiaLevel) and three properties. No paths, operations or existing properties change. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 35e78063-8202-487c-898f-021060a02c25
Contributor
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Member
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Az.FrontDoor AutoRest swagger pin to the Front Door API version 2026-04-01 so that generated output for Get-AzFrontDoorWafManagedRuleSetDefinition can surface new read-only WAF fields (DisplayName, Status, ParanoiaLevel) once regeneration happens, and documents the change in the module changelog.
Changes:
- Bumped the
FrontDoor.Autorestswaggercommit:pin and updated theinput-filepath tostable/2026-04-01. - Added an
## Upcoming Releasechangelog entry describing the new output properties for WAF managed rule set definitions.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/FrontDoor/FrontDoor.Autorest/README.md | Updates the AutoRest swagger pin (commit) and moves the swagger input-file to 2026-04-01. |
| src/FrontDoor/FrontDoor/ChangeLog.md | Adds user-facing release notes describing the new WAF output fields and the API version bump. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+22
to
+24
| * Added WAF managed rule set display name and status, and managed rule paranoia level, to `Get-AzFrontDoorWafManagedRuleSetDefinition` output. | ||
| - Added the `DisplayName` and `Status` properties to the returned rule sets. `Status` is one of `Preview`, `GA`, `Supported`, or `Deprecated`. | ||
| - Added the `ParanoiaLevel` property to the returned rules. It is set for DRS rules only and is empty for Bot Manager, DDoS, and AI rules. |
Comment on lines
30
to
32
| # pin the swagger version by using the commit id instead of branch name | ||
| commit: 3a617d58ce1d84caade01a3a682ec5c06a9088d9 | ||
| commit: 5d1343f93a5bb718e76ee017aa175cf8a697cb73 | ||
| require: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🤖 PR Validation —⚠️ Review suggested
️✔️Az.Accounts
Description
Bumps the
Az.FrontDoorswagger pin to API version2026-04-01soGet-AzFrontDoorWafManagedRuleSetDefinitionreturns three new read-only WAF fields:DisplayNameDefault Ruleset 2.2 (Latest, Recommended)StatusPreview,GA,Supported,DeprecatedParanoiaLevelPL1,PL2,PL3,PL4. Set for DRS rules only, empty for Bot Manager, DDoS and AI rulesToday these values are only visible in the portal. Users scripting WAF policy work have no way to tell which rule set version is current, which is deprecated, or which paranoia level a rule belongs to.
Az.FrontDoor is fully generated, so the change is the API version pin plus the changelog entry. No handwritten model or cmdlet code is involved.
Blast radius
2026-04-01is additive over2025-11-01. Compared against the merged spec it adds:ManagedRuleSetStatus,ParanoiaLevelManagedRuleSetDefinitionProperties.displayName,ManagedRuleSetDefinitionProperties.status,ManagedRuleDefinition.paranoiaLevelNo paths, operations, or existing properties are added, removed or changed. All three new properties are
readOnly, so there is no new input surface and no breaking change.Dependency, and why this is a draft
The spec is not merged yet. It is in Azure/azure-rest-api-specs PR 42373.
The
commit:pin above points at that PR head (5d1343f93a5bb718e76ee017aa175cf8a697cb73), which resolves today but is not onmain. Generated output is therefore not included in this PR: the pin has to be repointed at amaincommit once the spec merges, and regenerating now would only have to be redone. Once the spec lands I will repoint the pin, regenerate, refresh the markdown help, and take this out of draft.The matching Application Gateway change is Azure/azure-powershell PR 30023.
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.