Skip to content

Generate .NET SDK for Microsoft.Insights metric alerts 2024-03-01-preview version#53565

Draft
violetVo wants to merge 1720 commits intosdk-gen-trigger-metricAlert-preview-2024-03from
main
Draft

Generate .NET SDK for Microsoft.Insights metric alerts 2024-03-01-preview version#53565
violetVo wants to merge 1720 commits intosdk-gen-trigger-metricAlert-preview-2024-03from
main

Conversation

@violetVo
Copy link
Contributor

Contributing to the Azure SDK

Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.

For specific information about pull request etiquette and best practices, see this section.

Copy link
Member

@mrm9084 mrm9084 left a comment

Choose a reason for hiding this comment

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

Update for release

azure-sdk and others added 15 commits March 3, 2026 08:19
* Increment package version after release of Azure.Provisioning.Communication

* Increment package version after release of Azure.Provisioning.ContainerService
The focus of these changes is to propagate metadata
about the package visiblity and scope to each package
reference in the individual projects.  This allows
metadata tagging of references centrally, rather
than forcing every project to remember to specify
attributes like `PrivateAssets="All"` locally.
* Increment package version after release of Azure.Provisioning.Storage

* Update eng/centralpackagemanagement/Directory.Packages.props

---------

Co-authored-by: Jesse Squire <jesse.squire@gmail.com>
…celive root (#56689)

Co-authored-by: Emily Jiji <emilyjiji@microsoft.com>
The focus of these changes is to remove an owner flagged by the linter as no longer valid.   Riding along are a couple of minor formatting changes discovered along the way.
* initial mapping changes for supported context from shim

* pr comments
* initial mapping changes for supported context from shim

* pr comments
…alpha.20260303.2 (#56711)

* Regenerate repository SDK with TypeSpec build 20260303.2

* Update SDK code el_mo_2

* Update SDK code co_ed_1

* Update SDK code mo_sc_3

* Update SDK code se_wo_4

* Update SDK code ad_co_0
Replace references to non-existent release/Azure.Identity_1.18.0 branch
with main branch for ExperimentalFeatures.md links.

Related to #56525

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Ubuntu <cloudtest@0f79beacc000002.tkkhlgj2u51eln3mcb0lygmbye.dx.internal.cloudapp.net>
azure-sdk and others added 30 commits March 17, 2026 21:18
Adds a JSON Schema segment to the Azure.Core NuGet package that provides
IntelliSense for the AzureClients section in appsettings.json. Defines
retry, diagnostics, and azureOptions definitions matching the current
ClientOptions/RetryOptions/DiagnosticsOptions API surface.

Updates DiagnosticsOptions binding to use additive AdditionalLoggedHeaderNames
and AdditionalLoggedQueryParameters with case-insensitive deduplication,
matching the pattern established in System.ClientModel.

Resolves #56780

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…57196)

* Fix CodeTransparency unit test making real HTTP calls instead of using mock

The Snippet_Readme_CodeTransparencyVerification_Test was not passing its
MockTransport-configured options to VerifyTransparentStatement, causing
real HTTP calls to foo.bar.com that would timeout after ~7 minutes and
fail CI's 30-second global test limit.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Use #if SNIPPET/#else guard for snippet-safe mock transport usage

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* [EngSys] Agentic Triage Updates

 Rule Changes

  Customer evaluation (Step 2)

   - Bot allowlist matches now receive a bot label
     instead of customer-reported + question,
     distinguishing automation-filed issues from
     human customer issues

  Label prediction (Step 3)

   - Corrected Central-EngSys from service label
     to category label to match its actual
     repository color

   - Added Service as an excluded category alongside
    Central-EngSys — REST API/Azure service behavior
     issues require human judgment

   - Updated valid auto-triage categories to Client,
     Mgmt, and Provisioning only

   - Added explicit confidence exclusion checks for
     both Service and Central-EngSys predictions

   - Refined service label identification guidance:
     service labels typically match the service
     directory name "or the end of the package name"

  Rollback behavior

   - When triage cannot be fully completed — whether
     due to low confidence, excluded label prediction,
     or missing data — all previously applied labels
     are removed, leaving ONLY needs-triage as a
     clean slate for human reviewers

  Analysis comment (Step 6)

   - Added requirement to include label selection
     confidence and what alternative labels were
     considered, improving triage transparency

* Removing outdated agentic workflow version

* Tweaking wording to avoid over specificity

* Tweaking wording

* Fixing trigger condition to include non-priviledged users.
* Use new way to generate subclients

* Fix

* Fixes 2

* Update typespecs and regenerate code.
* Fix provisioning emitter package missing devDependencies for dotnet build /t:GenerateCode

Add azure-sdk/emitter-package-json-pinning array and missing devDependencies
(typespec-autorest, typespec-azure-rulesets, typespec-liftr-base, @typespec/openapi)
to the provisioning generator package.json, matching the mgmt generator.

The New-EmitterPackageJson.ps1 script uses this pinning array to generate the
emitter-package.json with correct devDependencies. Without it, tsp-client
fails to resolve transitive dependencies when running dotnet build /t:GenerateCode.

Fixes #57165

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Move emitter-package-json-pinning to end of package.json

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
)

Postpone release pending resolution of a critical issue.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Step 1: Init - add tsp-location.yaml, remove autorest.md, update csproj

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Step 5: Fix build errors - CodeGenSuppress for model factory overloads

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Step 6: ApiCompat - add nullable property shims for backward compat

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Step 8: Finalize - commit generated code and updated API surface

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Step 8: Add metadata.json for API version tracking

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Update test recordings for Communication MPG migration

Update recordings to match new TypeSpec-generated SDK:
- API version: 2023-04-01-preview -> 2026-03-18
- Remove Accept header from DELETE and no-body POST operations
- Remove empty properties from PATCH request bodies
- Fix identity.type spacing
- Fix domain name randomization

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Regenerate code after rebase on latest main

Fixes CI 'Verify Generated Code' failure by picking up latest generator
changes (Utf8JsonRequestContent -> RequestContent.Create pattern).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Rename Customized/ to Customize/ to match latest main convention

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* update spec commit id and regen

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Haiyuan Zhang <haiyzhan@microsoft.com>
* add config and regen

* temp commit

* regen

* regen

* regen

* regen

* temp commit

* regen

* regen

* regen

* regen by copilot cli

* temp commit

* regen

* regen

* regen

* regen by copilot cli, spec swagger changed

* regen

* Revert accidental network file changes - restore to upstream/main state

The Batch code generation accidentally modified two Network SDK files:
- ServiceGatewayListResult.cs: Added 'using Azure.ResourceManager.Batch' and changed field names
- VirtualNetworkApplianceResource.cs: Introduced BatchAccountCertificateResource references

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* WIP: Add back ApiCompatVersion and update BatchAccountPoolData custom code

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Regenerate Batch SDK with local spec repo and fix build errors

- Regenerated with local spec repo using @azure-typespec/http-client-csharp-mgmt@1.0.0-alpha.20260311.2
- Fixed SubResource.DeserializeSubResource generator bug (use ModelReaderWriter.Read with AOT context)
- Added backward-compat BatchAccountPoolCollection.CreateOrUpdate overloads (ETag?/string -> MatchConditions migration)
- Updated API surface files
- Updated code snippets

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix Batch SDK test recordings for TypeSpec migration

Update recording files to match new SDK behavior:
- Fix resource name mismatches caused by TestRandom offset
- Remove empty properties wrapper from ApplicationPackage requests
- Update assets.json tag to net/batch/Azure.ResourceManager.Batch_477b36b32d

All 27 non-skipped tests pass (0 failures).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix SubResource deserialization with CodeGenSerialization hook

Move SubResource.DeserializeSubResource workaround from Generated file to
Custom file using [CodeGenSerialization] DeserializationValueHook. This
survives code regeneration in CI.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Update commit hash in tsp-location.yaml

* fixed copilot review

* Regenerate Batch SDK with latest emitter (20260312.1)

Merge upstream main and regenerate code with the new mgmt emitter
version which replaces Utf8JsonRequestContent with RequestContent.Create().

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* temp

* Regenerate Batch SDK and add comments to custom classes

- Regenerated code with latest spec and generator
- Added detailed comments to BatchAccountPoolData explaining why
  DeploymentConfiguration is exposed as a custom public property
  (generator marks it internal due to flattenProperty on Pool.properties)
- Added comments to BatchNetworkConfiguration explaining the
  EndpointInboundNatPools backward compatibility property
- Fixed build error: PoolEndpointConfiguration.InboundNatPools is
  now read-only, always create new instance in setter

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* updated comments in custom code

* Update sdk/batch/Azure.ResourceManager.Batch/src/Custom/Models/BatchNetworkConfiguration.cs

Co-authored-by: Dapeng Zhang <ufo54153@gmail.com>

* Fix BatchNetworkConfiguration: replace AddRange with foreach loop and remove trailing whitespace

- IList<T> does not have AddRange; use foreach + Add instead
- Remove trailing whitespace on getter to fix SA1028

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Update tsp-location.yaml

---------

Co-authored-by: Arcturus Zhang <dapzhang@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Dapeng Zhang <ufo54153@gmail.com>
…lInsights to service directories (#57163)

* Move Azure.Provisioning ContainerRegistry, Dns, EventGrid, OperationalInsights to service directories

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix cross-package references: update paths for moved ContainerRegistry and OperationalInsights

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
npm does not walk up directories to find .npmrc, so create the
.npmrc dynamically in Agent.TempDirectory before running npm commands.
Pass NPM_CONFIG_USERCONFIG env var so npm finds it. Covers both the
emitter Initialize-WorkingDirectory steps and the tsp-client install.

Co-authored-by: jolov <jolov@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ff check (#57198)

* Remove static .npmrc from eng/packages

The .npmrc will be created dynamically by the create-authenticated-npmrc
pipeline step added to archetype-typespec-emitter.yml in azure-sdk-tools.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Exclude package-lock.json from generation diff check

The Check-CodeGeneration.ps1 diff check now excludes
package-lock.json since it can change when npm resolves packages
from a different registry (e.g. Azure DevOps feed vs npmjs.org)
which is not a meaningful code generation difference.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ions 10.4.0 (#56929)

Some of the [Experimental] surface area was tweaked while being promoted to stable.
* [Event Hubs] Update IoT Hub sample 

The focus of these changes is to update outdated text in the Event Hubs + IoT Hub example.
* Increment package version after release of Azure.AI.Extensions.OpenAI

* Increment package version after release of Azure.AI.Projects.Agents

* Increment package version after release of Azure.AI.Projects

* Update eng/centralpackagemanagement/Directory.Packages.props

---------

Co-authored-by: Jesse Squire <jesse.squire@gmail.com>
* Better streaming error reposring

* Fix
* Apply next renamings.

* Update hashes
* Prepare Azure.Provisioning.PrivateDns 1.0.0 stable release

- Bump version from 1.0.0-beta.2 to 1.0.0
- Update CHANGELOG.md with release date 2026-03-19

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Remove --prerelease flag from README install command

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…e, ContainerService to service directories (#57207)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…#57245)

* Update input-file URL for ContainerRegistry to point to 2026-01-01-preview API  specification

* Autogenerated SDK

* Exported apis

* Update CHANGELOG for 1.5.0-beta.2 release with new features and resource types

* Clarified features added in changelog

* Removed empty changelog entry sections

* remove empty blocks from changelog

* fix: Add naming conventions to ContainerRegistry autorest.md

Add prepend-rp-prefix entries for 33 new types lacking the ContainerRegistry
prefix (Archive, ExportPipeline, ImportPipeline, PipelineRun, SoftDeletePolicy,
EndpointProtocol, MetadataSearch, PipelineOption, SyncState, SyncTrigger, etc.)

Add rename-mapping entries for forbidden suffix violations:
- PipelineRunRequest -> ContainerRegistryPipelineRunContent
- PipelineRunResponse -> ContainerRegistryPipelineRunResult
- RegistrySyncResult -> ContainerRegistrySyncResult

Code must be regenerated with 'dotnet build /t:GenerateCode' to apply changes.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* regen and export API

---------

Co-authored-by: Wei Hu <huwe@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI Model Inference AI Projects Client This issue is related to a non-management package CodeGen Issues that relate to code generation Event Grid Health Deidentification Image Analysis KeyVault Mgmt This issue is related to a management package. Monitor - Query Provisioning Schema Registry

Projects

Status: Untriaged

Development

Successfully merging this pull request may close these issues.