Closed azure-pipelines[bot] closed 2 weeks ago
Thank you for your contribution azure-pipelines[bot]! We will review the pull request and get back to you soon.
/azp run
/azp run azure-powershell - security-tools
To the author of the pull request, This PR was labeled "Breaking Change Release" because it contains breaking changes.
Description
Migrate DesktopVirtualization from generation to main The last commit of src/DesktopVirtualization in generation is: commit 6174dd58b94f17dc0b6a0740a422205f7b802832 Author: Alec Baird 100880612+alec-baird@users.noreply.github.com Date: Mon Nov 4 22:01:15 2024 -0700 Alecb/generation 20240403 Stable Release (#25951) built new module on stable, all tests pass Updated examples Added missing custom powershell and tests, renamed Senerio to Scenario Ran tests after adding custom posh Added breaking change supporessions for upgraded commonTypes from v2 to v5 Ran autorest v4 added v4 directives Committing work for v4 upgrade, Updated custom cmdlets to use autorest v4, lost function exports for PrivateLink Updated custom to v4, removed PrivateLink from export Fixed PEC and PLR cmdlets, removed breaking change issues to check status Added breakingChangeExceptions, all tests pass but RemoveSH All tests pass Empty Commit to run CI again because I don't have run perms added identity to readme Empty commit to re-run CI Added Examples back that were lost from v4 Removed BreakingChangeIssues to determine what changes we have Added breaking change exceptions (largely due to autorest v3 -> v4 and swagger commontypes v2 -> v5 built module with removed directive and reverted versioning * Removed comment
Checklist
[x] Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:
SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to generation branch.
SHOULD make the title of PR clear and informative, and in the present imperative tense.
SHOULD update ChangeLog.md file(s) appropriately
SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
SHOULD have proper test coverage for changes in pull request.
SHOULD NOT introduce breaking changes in Az minor release except preview version.
SHOULD NOT adjust version of module manually in pull request