[PS][Monitor] Add breaking change message for MonitorWorkspace #28224
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 adds breaking change messages for the MonitorWorkspace module, specifically documenting upcoming changes to the output properties of Get, New, and Update cmdlets. The changes include regenerated module files and solution project reorganization.
Key Changes
- Added breaking change configuration for MonitorWorkspace cmdlets regarding PrivateEndpointConnection and ProvisioningState properties
- Regenerated module files including new AssemblyInfo.cs and updated GUIDs
- Updated solution file to reorganize MonitorWorkspace project structure
Reviewed Changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| src/Monitor/MonitorWorkspace.Autorest/README.md | Added breaking change directive for Get/New/Update cmdlets with property type changes |
| src/Monitor/Monitor/ChangeLog.md | Updated changelog to include MonitorWorkspace cmdlets in breaking changes section |
| src/Monitor/Monitor.sln | Reorganized solution structure for MonitorWorkspace project |
| src/Monitor/MonitorWorkspace.Autorest/Properties/AssemblyInfo.cs | Added new assembly information file |
| src/Monitor/MonitorWorkspace.Autorest/generate-info.json | Updated generation ID |
| src/Monitor/MonitorWorkspace.Autorest/docs/Az.MonitorWorkspace.md | Updated module GUID |
| src/Monitor/MonitorWorkspace.Autorest/resources/README.md | Added new resources directory documentation |
YanaXu
approved these changes
Jul 22, 2025
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.