[KeyVault] Use 4.x autorest version, Regenerated sdk #28708
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. |
There was a problem hiding this comment.
Pull Request Overview
This PR updates the Azure PowerShell KeyVault module to use the latest 4.x version of the AutoRest PowerShell generator instead of the pinned 4.0.631 version, and regenerates the SDK accordingly.
Key Changes:
- Updated AutoRest PowerShell generator version from 4.0.631 to 4.x
- Regenerated the KeyVault Management SDK with the new generator version
notyashhh
changed the title
notyashhh
commented
Oct 16, 2025
| /// set to true a unique x-ms-client-request-id value is generated and | ||
| /// included in each request. Default is true. | ||
| /// Whether a unique x-ms-client-request-id should be generated. When | ||
| /// /// set to true a unique x-ms-client-request-id value is generated and |
There was a problem hiding this comment.
There are double comments generated. I believe this is a known issue in autorest. So no problem for this sdk!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.