Refresh azure-mgmt-alertprocessingrules after migrate to Typespec#47960
Conversation
…osoft.AlertsManagement/AlertProcessingRules/tspconfig.yaml', API Version: 2021-08-08, SDK Release Type: beta, and CommitSHA: '360b77c3130197756d9affa3708d646f3b8e3a0f' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6538270 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
There was a problem hiding this comment.
Pull request overview
This PR refreshes the azure-mgmt-alertprocessingrules management library after its migration to TypeSpec (API version 2021-08-08, beta release). It introduces a brand-new package under sdk/alertsmanagement/ that splits Alert Processing Rules CRUD operations into their own client, and wires the package into the service CI.
Changes:
- Adds the new
azure-mgmt-alertprocessingrulespackage (client, config, models, operations, types) generated from TypeSpec, versioned1.0.0b1. - Adds packaging/config scaffolding (pyproject.toml, README, CHANGELOG, LICENSE, MANIFEST.in, dev_requirements, tsp-location, api/metadata files).
- Registers the new artifact in
sdk/alertsmanagement/ci.yml.
Reviewed changes
Copilot reviewed 52 out of 52 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
ci.yml |
Adds azure-mgmt-alertprocessingrules artifact; format matches existing entry |
_version.py |
Sets VERSION = "1.0.0b1", consistent with CHANGELOG |
CHANGELOG.md |
Initial 1.0.0b1 (2026-07-09) entry; date matches current date |
pyproject.toml |
Preview flags correct: is_stable=false, Beta classifier, title=AlertProcessingRulesMgmtClient |
_client.py (sync/aio) |
Client signature order credential, subscription_id, base_url; name consistent with README/pyproject |
README.md |
Sample code matches client signature |
tsp-location.yaml / _metadata.json |
Spec source/commit references for regeneration |
apiview-properties.json / api.md / api.metadata.yml |
Generated API surface snapshots |
MANIFEST.in / LICENSE / dev_requirements.txt |
Standard packaging scaffolding |
| Generated source/samples/tests | Emitted by TypeSpec generator (excluded from detailed mgmt review) |
All applicable mgmt review checklist items pass: version consistency, changelog date, stability flags, client __init__ parameter order, subscription_id present (so no_sub not required), and client-name consistency across _client.py, README.md, and pyproject title. I found no objective issues within the reviewable scope, so I have no line comments.
|
/azp run prepare-pipelines |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Configurations: 'specification/alertsmanagement/resource-manager/Microsoft.AlertsManagement/AlertProcessingRules/tspconfig.yaml', API Version: 2021-08-08, SDK Release Type: beta, and CommitSHA: '360b77c3130197756d9affa3708d646f3b8e3a0f' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6538270 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
Namespace review issue: Azure/azure-sdk#9441