Removed the deprecated classic alerts spec

[grchris-microsoft]

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

• New resource provider.
• New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
• Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
• Update existing version to fix OpenAPI spec quality issues in S360.
• Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
• Other, please clarify:
  • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

• I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
• I have reviewed following Resource Provider guidelines, including
  ARM resource provider contract and
  REST guidelines (estimated time: 4 hours).
  I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

• First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
  This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

[heaths]

This is impossible to review:

Please rebase your commits on main and force push to this PR. Assuming your fork is origin and this repo is upstream:

git fetch upstream main
git checkout grchris-microsoft/remove_classic_alerts_specs # assuming it's not checked out already
git rebase upstream/main
git push --force

[grchris-microsoft]

Hi, I really apologize for the confusion, but this is not the correct PR. It tries to merge it to Master branch, while the correct one is called main. I couldn't find an easy way to update this PR, so I created a new one. Here is another one with similar changes. Please take a look: #30787 This PR removes the resource type called alertRules. That resource type was deprecated on the public cloud about three years ago. Now it is completely deprecated in sovereign clouds as well. The complete Deprecation was announced in February, and since then, even a bit earlier, no one uses that service. In August, we completely deleted all the resources of this resource type. This PR is marked as a breaking change, but actually it is kind of cleanup. Please let me know what should be my next steps Thank you, Gregory Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Heath Stewart ***@***.***> Sent: Monday, September 30, 2024 11:38:47 PM To: Azure/azure-rest-api-specs ***@***.***> Cc: Gregory Chris ***@***.***>; Author ***@***.***> Subject: Re: [Azure/azure-rest-api-specs] Removed the deprecated classic alerts spec (PR #30785) This is impossible to review: image.png (view on web)<https://github.com/user-attachments/assets/ad7e7564-44f8-4237-a4e6-240353b5e66f> Please rebase your commits on main and force push to this PR. Assuming your fork is origin and this repo is upstream: git fetch upstream main git checkout grchris-microsoft/remove_classic_alerts_specs # assuming it's not checked out already git rebase upstream/main git push --force — Reply to this email directly, view it on GitHub<#30785 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASKBK2FZGIQUCWYUTU4TBWTZZGZFPAVCNFSM6AAAAABPBUYHJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBUGEYDGMJQGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>