Skip to content

[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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

JoyerJin
Copy link
Contributor

@JoyerJin JoyerJin commented Jul 18, 2025

Description

Mandatory Checklist

  • SHOULD update ChangeLog.md file(s) appropriately
    • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
      • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
    • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  • SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
  • SHOULD have proper test coverage for changes in pull request.
  • SHOULD NOT adjust version of module manually in pull request

Copy link

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

@JoyerJin JoyerJin marked this pull request as ready for review July 21, 2025 07:55
@Copilot Copilot AI review requested due to automatic review settings July 21, 2025 07:55
Copy link
Contributor

@Copilot Copilot AI left a 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

@YanaXu
Copy link
Contributor

YanaXu commented Jul 21, 2025

/azp run

Copy link
Contributor

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.

@YanaXu
Copy link
Contributor

YanaXu commented Jul 21, 2025

/azp run

Copy link
Contributor

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.

@YanaXu
Copy link
Contributor

YanaXu commented Jul 22, 2025

/azp run

Copy link
Contributor

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.

@YanaXu
Copy link
Contributor

YanaXu commented Jul 22, 2025

/azp run

Copy link
Contributor

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.

@YanaXu
Copy link
Contributor

YanaXu commented Jul 22, 2025

/azp run

Copy link
Contributor

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.

@YanaXu
Copy link
Contributor

YanaXu commented Jul 22, 2025

/azp run

Copy link
Contributor

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.

@JoyerJin JoyerJin added the Breaking Change Preannounce This PR adds preannouncement about upcoming breaking change label Jul 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaking Change Preannounce This PR adds preannouncement about upcoming breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants