Skip to content

[ApplicationInsights] added breaking change warnings #17672

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

Merged

Conversation

VeryEarly
Copy link
Collaborator

Description

added breaking change warnings for upcoming Az.ApplicationInsights 2.0.0

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:
    • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • the markdown help files have been regenerated using the commands listed here

using System.Management.Automation;

namespace Microsoft.Azure.Commands.ApplicationInsights
{
[GenericBreakingChange("API version bump up to 2020-02, output type will be also updated to match the new API version", "2.0.0")]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The API version contains date, does it? like 2020-02?

@BethanyZhou BethanyZhou merged commit 9469e12 into Azure:release-2022-04-05 Mar 31, 2022
@VeryEarly VeryEarly deleted the yabo/applicationinsights branch March 31, 2022 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants