-
Notifications
You must be signed in to change notification settings - Fork 4k
[PS][Monitor] Add breaking change for ScheduledQueryRule #28227
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
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
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 adds breaking change annotations for the ScheduledQueryRule module, indicating that certain parameter and output property types will change from arrays to lists in a future release. The changes include reorganizing the module structure by moving it from a generated location to the src directory and adding comprehensive breaking change warnings.
- Added breaking change attributes to parameters (Value, Dimension) and output properties (ActionGroup, CriterionAllOf, Scope, TargetResourceType)
- Moved ScheduledQueryRule module from generated directory to src directory structure
- Updated changelog to document the breaking changes for affected cmdlets
Reviewed Changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated 4 comments.
Show a summary per file
File | Description |
---|---|
src/Monitor/ScheduledQueryRule.Autorest/resources/README.md | Added new documentation file explaining the resources directory structure |
src/Monitor/ScheduledQueryRule.Autorest/generate-info.json | Updated generation ID for the module |
src/Monitor/ScheduledQueryRule.Autorest/docs/Az.ScheduledQueryRule.md | Updated module GUID in documentation |
src/Monitor/ScheduledQueryRule.Autorest/custom/New-AzScheduledQueryRuleDimensionObject.ps1 | Added breaking change attribute for Value parameter |
src/Monitor/ScheduledQueryRule.Autorest/custom/New-AzScheduledQueryRuleConditionObject.ps1 | Added breaking change attribute for Dimension parameter |
src/Monitor/ScheduledQueryRule.Autorest/README.md | Added breaking change directives for parameters and output properties |
src/Monitor/ScheduledQueryRule.Autorest/Properties/AssemblyInfo.cs | Added new assembly information file |
src/Monitor/Monitor/ChangeLog.md | Updated changelog with breaking change information for ScheduledQueryRule cmdlets |
src/Monitor/Monitor/Az.Monitor.psd1 | Updated generation date |
src/Monitor/Monitor.sln | Reorganized project references for ScheduledQueryRule module |
src/Monitor/ScheduledQueryRule.Autorest/custom/New-AzScheduledQueryRuleDimensionObject.ps1
Show resolved
Hide resolved
src/Monitor/ScheduledQueryRule.Autorest/custom/New-AzScheduledQueryRuleConditionObject.ps1
Show resolved
Hide resolved
/azp run |
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
/azp run |
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
/azp run |
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
/azp run |
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
/azp run |
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
/azp run |
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
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.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.