Repository navigation
Conversation
Regenerate CDN and Front Door cmdlets, expose gRPC and capacity-based load balancing, retain standalone EdgeAction commands, and add offline API regression coverage. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: bba26f90-f8d3-4432-99b6-58230191fcad
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
|
Thank you for your contribution Zaaaaaa! We will review the pull request and get back to you soon. |
|
/azp run |
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
X Engineering Agent ReportReview — Comments Human review-only: corrections remain; no approval or readiness handoff. Upstream snapshot: 13 completed checks, 5 passed, 8 failed, 0 pending. The failures collapse into 2 grouped builds and 6 task diagnostics (4 playback, 2 static analysis), all PR-related by quoted/current-source evidence. Two deduplicated findings below; no Agent tests or CI re-polling. Reviewed head Upstream CIpowershell-core
windows-powershell
Test validation
The repo-aware helper is not applicable to PowerShell; that is not an Az.Cdn coverage pass. Independently inspected Recording risk / confirmed gap: No recording changed. At this head, Focused verification requested (not executed): In the existing Az.Cdn module test environment, run Confirmed findings
No additional semantic defect was confirmed from the review questions. Lesson matches and pending Copilot reviewer feedback were empty. The pinned generator input and changed generation markers are present; this source review does not independently attest execution of the approved Codegen flow. Risk assessment — 71/100 · HighThe High rating is driven by security-sensitive behavior, public CLI behavior, generated output.
Posted by x-engineering-agent (Reviewer) |
Regenerate against the pinned 2026-09-01-preview specification, add authorization policy cmdlets and helpers, and cover serialization, HTTP handling, and ClientResponse with offline tests. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: bba26f90-f8d3-4432-99b6-58230191fcad
|
/azp run |
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
🤖 PR Validation — ❌ Action needed
️✔️Az.Accounts
❌Az.Cdn
Description
Upgrade the independent Az.Cdn preview module from service API
2026-04-01-previewto2026-09-01-preview, including the authorization policy changes from Azure/azure-rest-api-specs#46300. This PR intentionally targetsAz.Cdn-preview, notmainor the legacypreviewbranch, following the Azure PowerShell team's preview-branch guidance.dad386cfa12e742067b181a446f44ab55bd0fd7cand update the AutoRest inputs, generated client/cmdlets, UX metadata, and help.Get,New,Update, andRemove-AzFrontDoorCdnAuthPolicy, including list/get, identity, JSON, and long-running-operation support.New-AzFrontDoorCdnAuthPolicyEntraIdConfigObjectandNew-AzFrontDoorCdnAuthPolicyAssociationObjectfor Microsoft Entra ID validation and profile/domain/route associations. Expose policy action and token-forwarding settings.ClientResponseinvocation point for EdgeAction delivery-rule actions.2024-07-22-preview/edgeaction.jsonand all 16 standalone EdgeAction resource cmdlets, plus existing mTLS, WAF associations, origin authentication token destination headers, and URL signing.Release coordination: This remains a Draft for Azure PowerShell team review and approval, targeting a November 2026 independent public preview. Module/package version numbers have not been manually changed. Public API/design approval and preview package versioning/publication remain with the PowerShell team.
The companion general-release PR #30293 targets
main, uses API2026-10-01, and removes the previously announced standalone EdgeAction resource cmdlets. That removal is not part of this preview PR, and the companion PR was not changed by this update.Specification dependency: The September input is pinned to the unmerged head of azure-rest-api-specs#46300. Specification merge and availability of the September RP API remain release gates.
Validation
falsevalues, omitted PATCH settings, read-only property exclusion, GET/list/PUT/PATCH/DELETE request and response handling, error propagation, and synchronous/asynchronous HTTP fixtures. HTTP fixtures are not live service validation.git diff --check. The two generated in-memory helpers follow the generator's existing ShouldProcess convention.NuGet.Configwas not changed. The successful scoped analyzer checks do not replace repository static analysis.CI must run against this PR's latest commit. An upstream owner or collaborator with Write access must authorize
azp run; the existing bot results for the earlier commit do not validate this update. Updated recordings through the authorized live-test process, CI, specification/RP readiness, and PowerShell team approval are required before this Draft becomes merge-ready.Mandatory Checklist
Please choose the target release of Azure PowerShell. (Target release is different from API readiness.)
I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriately.src/Cdn/Cdn/ChangeLog.mdunder## Upcoming Release.