-
Notifications
You must be signed in to change notification settings - Fork 4.1k
upgrade websites module to autorest v4 #28268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
bf40356
to
345bc0f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR upgrades the Azure PowerShell Websites module to use AutoRest v4, introducing various new features and breaking changes.
- Upgrades the code generator from AutoRest v3 to v4, bringing new parameter sets and parameter types
- Updates cmdlet signatures, particularly for Static Web App cmdlets with new identity management parameters
- Changes many API response models from versioned namespaces to unversioned interfaces
Reviewed Changes
Copilot reviewed 112 out of 112 changed files in this pull request and generated 1 comment.
File | Description |
---|---|
tools/StaticAnalysis/Exceptions/Az.LoadTesting/BreakingChangeIssues.csv | Documents breaking changes including type changes, removed parameters, and removed parameter sets |
src/Websites/Websites/help/*.md | Updates documentation for cmdlets with new parameter sets, type changes, and corrected descriptions |
src/Websites/Websites/ChangeLog.md | Documents the upgrade and breaking changes for New-AzStaticWebApp identity parameters |
src/Websites/Websites/Az.Websites.psd1 | Updates module metadata including required Az.Accounts version and file paths |
### Example 2: Create or updates the app settings of a static site build by pipeline | ||
```powershell | ||
Get-AzStaticWebAppBuildAppSetting -ResourceGroupName resourceGroup -Name staticweb00 -EnvironmentName 'default' | New-AzStaticWebAppBuildAppSetting -AppSetting @{'buildsetting1' = 'someval'; 'buildsetting2' = 'someval2' } | ||
Get-AzStaticWebAppBuildAppSetting -ResourceGroupName resourceGroup -Name taticweb00 -EnvironmentName 'default' | New-AzStaticWebAppBuildAppSetting -AppSetting @{'buildsetting1' = 'someval'; 'buildsetting2' = 'someval2' } |
Copilot
AI
Aug 6, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a typo in the example: 'taticweb00' should be 'staticweb00' to match the expected static web app naming convention.
Get-AzStaticWebAppBuildAppSetting -ResourceGroupName resourceGroup -Name taticweb00 -EnvironmentName 'default' | New-AzStaticWebAppBuildAppSetting -AppSetting @{'buildsetting1' = 'someval'; 'buildsetting2' = 'someval2' } | |
Get-AzStaticWebAppBuildAppSetting -ResourceGroupName resourceGroup -Name staticweb00 -EnvironmentName 'default' | New-AzStaticWebAppBuildAppSetting -AppSetting @{'buildsetting1' = 'someval'; 'buildsetting2' = 'someval2' } |
Copilot uses AI. Check for mistakes.
To the author of the pull request, |
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.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.