fix front door ternary operator issue #28831
Merged
Conversation
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
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR migrates the FrontDoor module to AutoRest PowerShell V4 and ensures PowerShell 5.1 compatibility by replacing ternary operators with if-else blocks. Key changes include:
- Replaced PowerShell 7.0+ ternary operators with PowerShell 5.1-compatible if-else blocks in routing rule and rules engine cmdlets
- Updated help documentation URL casing
- Regenerated AutoRest artifacts (GUIDs, generate_Id)
Reviewed Changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| src/FrontDoor/FrontDoor/help/New-AzFrontDoorBackendPoolsSettingObject.md | Updated online help URL with correct module name casing |
| src/FrontDoor/FrontDoor/Az.FrontDoor.psd1 | Updated generated date timestamp |
| src/FrontDoor/FrontDoor.sln | Regenerated project GUIDs for AutoRest project reference |
| src/FrontDoor/FrontDoor.Autorest/generate-info.json | Updated AutoRest generation identifier |
| src/FrontDoor/FrontDoor.Autorest/docs/Az.FrontDoor.md | Updated module GUID after regeneration |
| src/FrontDoor/FrontDoor.Autorest/custom/New-AzFrontDoorRulesEngineActionObject.ps1 | Replaced ternary operators with if-else blocks for PowerShell 5.1 compatibility |
| src/FrontDoor/FrontDoor.Autorest/custom/New-AzFrontDoorRoutingRuleObject.ps1 | Replaced ternary operators with if-else blocks for PowerShell 5.1 compatibility |
src/FrontDoor/FrontDoor/help/New-AzFrontDoorBackendPoolsSettingObject.md
Outdated
Show resolved
Hide resolved
Member
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
6 tasks
Member
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
dolauli
approved these changes
Nov 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
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.