[PS] Migrate StackHCI module to autorest v4 #28363
Open
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. |
There was a problem hiding this comment.
Pull Request Overview
This PR migrates the StackHCI module from autorest v3 to autorest v4, updating generated PowerShell cmdlets and their documentation. The migration brings several structural changes to the module's API surface.
Key changes include:
- Updated type definitions from strongly-typed enums to string types for better flexibility
- Modified parameter sets and method signatures across cmdlets
- Added new JSON input parameter support for several cmdlets
- Restructured identity and authentication parameter handling
Reviewed Changes
Copilot reviewed 83 out of 84 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| help/*.md | Updated cmdlet documentation with new parameter types and syntax changes |
| StackHCI.sln | Updated project GUID references for autorest v4 compatibility |
| Az.StackHCI.psd1 | Added new cmdlet exports and updated module metadata |
| test/utils.ps1 | Fixed variable references in test utility functions |
| docs/*.md | Updated autorest documentation with new type definitions |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
waiting the service team for recording test |
isra-fel
added
the
autorest v4 migration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.