-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Migrate Devtestlabs to generate from TypeSpec #53452
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
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 migrates the DevTestLabs SDK to generate from TypeSpec by updating the autorest configuration. The primary change is updating the OpenAPI specification reference to a newer commit and adding extensive swagger transformation directives to handle property definitions and parameter descriptions.
Key Changes:
- Updated the OpenAPI specification reference to a newer commit (471eab6)
- Removed an unused rename mapping for
WindowsOSState - Added multiple swagger transformation directives to remove
additionalPropertiesfrom various definitions and standardize parameter descriptions
| $["description"] = "The name of the notification channel"; | ||
| } | ||
| if ($["description"] && $["description"].includes("LabVirtualMachine")) { | ||
| $["description"] = "The name of the virtual machine"; |
Copilot
AI
Oct 23, 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.
Inconsistent spacing in description strings. This line correctly has no leading space, but lines 222-237 have extra leading spaces. All description strings should have consistent formatting without leading spaces.
Continue work of #51337
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.