Skip to content

Migration guide for autorest v4 upgrade #28760

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.

Sign up for GitHub

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Migration guide for autorest v4 upgrade #28760

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions documentation/migration-guides/Az.15.0.0-migration-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
## Modules migrated from autorest v3 to autorest v4

To maintain behavioral consistency and introduce new features supported by AutoRest v4, we have upgraded many modules to use AutoRest v4.
This upgrade has introduced several breaking changes.
Details about potential breaking changes and their mitigation approaches can be found at the following [link](https://go.microsoft.com/fwlink/?linkid=2333486).

### Potentially affected modules
- Az.Advisor
- Az.ApplicationInsights
- Az.ArcResourceBridge
- Az.Attestation
- Az.Automanage
- Az.Compute
- Az.ConfidentialLedger
- Az.ContainerRegistry
- Az.Databricks
- Az.Dns
- Az.HealthcareApis
- Az.LoadTesting
- Az.Monitor
- Az.NetworkCloud
- Az.Nginx
- Az.Relay
- Az.StorageMover
- Az.StreamAnalytics
- Az.Workloads