Skip to content

Updating stable release branch#41047

Open
jeremyfrosti wants to merge 2540 commits into
release-sql-Microsoft.Sql-2025-01-01from
main
Open

Updating stable release branch#41047
jeremyfrosti wants to merge 2540 commits into
release-sql-Microsoft.Sql-2025-01-01from
main

Conversation

@jeremyfrosti

Copy link
Copy Markdown
Member

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.

spec_pr_review_workflow_diagram

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.
  • A release plan has been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

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.
  • For guidance on SDK breaking change review, refer to https://aka.ms/ci-fix.

@github-actions

github-actions Bot commented Mar 5, 2026

Copy link
Copy Markdown

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ The suppressions added to the AutoRest config files (README.mds) require review. Refer to step 1 in the PR workflow diagram, or to step 3, depending on the kind of suppression you did.

Important checks have failed. As of today they are not blocking this PR, but in near future they may.
Addressing the following failures is highly recommended:
  • ⚠️ The check named SDK Validation Status has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide


Comment generated by summarize-checks workflow run.

@github-advanced-security

Copy link
Copy Markdown
Contributor

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

jliusan and others added 13 commits June 16, 2026 01:15
* mitigate breaking change for kusto

* update

* Revert "update"

This reverts commit 174cc99.
…43746)

* Add examples for FileSystems operations in Qumulo.Storage API

- Created maximum and minimum set examples for FileSystems_CreateOrUpdate.
- Added maximum and minimum set examples for FileSystems_Delete.
- Introduced maximum and minimum set examples for FileSystems_Get.
- Added examples for listing FileSystems by resource group and subscription, both maximum and minimum sets.
- Created maximum and minimum set examples for FileSystems_Update.
- Added examples for Operations_List, including maximum and minimum sets.

* Update Qumulo.Storage API examples and specifications for 2026-04-16 release

- Modified example JSON files for FileSystems_Get, FileSystems_ListByResourceGroup, FileSystems_ListBySubscription, and FileSystems_Update to reflect new API version and updated parameters.
- Added new examples for maximum and minimum sets for various operations.
- Updated readme files for C#, Go, Python, and TypeScript to include new settings and paths for the 2026-04-16 version.
- Introduced suppressions for breaking changes in the SDKs and removed outdated suppressions.
- Adjusted the module names and package names in the Go and Python readme files for consistency with the new structure.

* Remove unused example references and 'NotSpecified' state from Qumulo.Storage API specifications

* Add TypeSpec examples for preview versions and regenerate swagger with x-ms-examples

* Remove performanceTier from 2025-10-01-preview Update example request body

* Suppress PatchBodyParametersSchema lint errors for Qumulo.Storage

* Add qumulostorage to cspell dictionary

* Remove tag definitions for non-existent swagger versions

* Remove redundant Resource model definition from FileSystemResourceProperties

* Remove BaseResourceProperties model from UserDetails

* Replace legacy @azure-tools/typespec-csharp with @azure-typespec/http-client-csharp-mgmt

---------

Co-authored-by: Navjot Kaur <kaurnavjot@microsoft.com>
* fix: update service-name for Java typespec to AzureSphere

* fix: update service-name to "Azure Sphere" in tspconfig and add validation trigger in client.tsp

* fix: update flattenProperty annotation to exclude Java for ProductUpdate, DeviceGroupUpdate, and DeviceUpdate models

* Update client.tsp
* Added SharedLimitCaps typespec

* fix prettier check and readme

* fixes for typespec validation

* fix JS SDK error and prettier

* refactor APIs

* addressed comments

* added examples

* fix description

* added post operation

* remove example for JS SDK validation

* addressed comments

* add location scope

---------

Co-authored-by: Teodor Abeaboeru <tabeaboeru@microsoft.com>
…44009)

* Import client.tsp from main.tsp for services with no spec impact

* Import client.tsp with omit-unreachable-types for applink, edge, relationships
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: mikeharder <9459391+mikeharder@users.noreply.github.com>
Co-authored-by: Mike Harder <mharder@microsoft.com>
weidongxu-microsoft and others added 30 commits July 6, 2026 10:35
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add ResourceGraph provisioning emitter config

* Fix ResourceGraph provisioning output path
* [liftrmongodb] Add C# clientName renames for tier/region models

Rename RegionsByTierResponse, TierLimitReachedResponse, TierRegions, and ProjectLimitStatus to MongoDBAtlas*-prefixed C# names. The two Response models also adopt the 'Result' suffix to satisfy the AZC0030 analyzer. Client-only (csharp) renames; the wire contract is unchanged.

* [liftrmongodb] Use PascalCase ClusterTier member names (Free/Flex) for csharp

* [liftrmongodb] Rename backups property to IsBackupsEnabled for csharp

Add @@clientName rename for ClusterProperties.backups -> IsBackupsEnabled
to satisfy BOOL001 (.NET bool properties need Is/Has/Can prefix).
Wire name and nullability unchanged.

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

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add FrontDoor provisioning emitter config

* Preserve FrontDoor provisioning type names

* Hide FrontDoor frontend endpoint operations for provisioning

* Preserve FrontDoor frontend endpoint resource name

* Remove FrontDoor endpoint compatibility overrides

* Apply suggestion from @ArcturusZhang

---------

Co-authored-by: JialinHuang803 <139532647+JialinHuang803@users.noreply.github.com>
#44433)

Preserve the existing Python SDK client name DynatraceObservabilityMgmtClient
via @@clientName python override to prevent a breaking change when the SDK is
regenerated from TypeSpec.

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

Preserve the existing Python SDK client name EdgeOrderManagementClient
via @@clientName python override to prevent a breaking change when the SDK is
regenerated from TypeSpec.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Set the Python SDK client name to PowerBIDedicatedMgmtClient via @@clientName
python override for the Microsoft.PowerBIDedicated TypeSpec.

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

Preserve the existing Python SDK client name PrivateDnsManagementClient
via @@clientName python override to prevent a breaking change when the SDK is
regenerated from TypeSpec. Mirrors the existing javascript and java overrides.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…esource rename (#44440)

- Set the Python SDK client name to RelayAPIMgmtClient via @@clientName python override.
- Remove the no-longer-needed @@clientName ArmResource python override from back-compatible.tsp.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Set the Python SDK client name to StorageSyncMgmtClient via @@clientName python
override for the Microsoft.StorageSync TypeSpec.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Enable Compute provisioning emitter

* Rename Compute provisioning resources for CSharp

* Pin Compute provisioning API versions

* Use stable Compute provisioning API version

* Revert "Rename Compute provisioning resources for CSharp"

This reverts commit 2aecc63.

* Use Compute provisioning API version map

* Remove Compute provisioning API version pin
Set the Python SDK client name to ElasticMgmtClient via @@clientName python
override for the Microsoft.Elastic TypeSpec.

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

* CognitiveServices: add C# type renames and fix wildcard doc escaping

- Rename 12 types with generic names to include service-specific prefixes (CognitiveServices/Deployment) scoped to csharp
- Update existing ReplacementConfig rename to CognitiveServicesModelReplacementConfiguration
- Fix wildcard '*' in RaiEgressRuleMatch docs rendering as <i></i> in generated XML docs
- Refresh swagger output from tsp compile

* Retrigger CI
…ta' (#44444)

according to Azure/azure-sdk-pr#2644, rename JS package from '@azure/arm-azurearcdata' to '@azure/arm-arcdata'
… for .NET SDK (#44371)

* Fix to allow customers pass in the location along with resource group and make them public.

* Resetting the names to validate SDK behavior

* Renamed the specific ScheduledAction names to BulkAction as a new .NET SDK version would be shipped and the prior release would be altered.

* Replace Type suffix with Kind suffix to adhere to .NET naming convention.

---------

Co-authored-by: Sumedh Sandeep Parvatikar <sparvatikar@microsoft.com>
* Support: add new stable API version 2026-06-15

Introduces the 2026-06-15 stable API version for Microsoft.Support,
including ProblemClassifications_ClassifyProblems. Follows the new-api-version
pattern from PR #43591 (which introduced 2026-06-01):

- main.tsp: add v2026_06_15 to the Versions enum (armCommonTypesVersion v5)
- examples/2026-06-15: copy of 2026-06-01 examples with api-version bumped
- stable/2026-06-15/support.json: regenerated via tsp compile
- readme.md: add package-2026-06-15 tag and set it as the default

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

* Support: add optional articleId to ClassifyProblems response (2026-06-15)

Adds an optional, read-only string property 'articleId' to
ProblemClassificationsClassificationResult, gated with @added(Versions.v2026_06_15)
so it is the only API difference between 2026-06-15 and the prior 2026-06-01 version.

- models.tsp: add articleId?: string (@visibility Read, @added v2026_06_15)
- examples/2026-06-15: demonstrate articleId in both ClassifyProblems responses
- stable/2026-06-15/support.json (+ examples): regenerated via tsp compile

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

* Support: make ClassifyProblems response articleId nullable (2026-06-15)

Allow articleId to be explicitly null in addition to being optional/empty,
per requirement. Adds x-nullable to the generated schema.

- models.tsp: articleId?: string -> articleId?: string | null, with a
  #suppress for @azure-tools/typespec-azure-core/no-nullable and justification
- stable/2026-06-15/support.json: regenerated (articleId now x-nullable: true)

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

* Support: clarify articleId availability in description (2026-06-15)

Note that articleId is only populated when Alchemy responds.

- models.tsp: extend articleId doc comment
- stable/2026-06-15/support.json: regenerated description

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

* Support: refine articleId description for public docs (2026-06-15)

Replace internal service reference with customer-observable behavior:
articleId is populated only when a related article is available.

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

* Support: rename new API version 2026-06-15 -> 2026-07-01

Renames the in-progress stable API version from 2026-06-15 to 2026-07-01
across all references:

- main.tsp: Versions enum member v2026_06_15 -> v2026_07_01 (value "2026-07-01")
- models.tsp: articleId @added(Versions.v2026_07_01)
- readme.md: package-2026-07-01 tag (default) + input-file path
- examples/2026-07-01: renamed from examples/2026-06-15, api-version bumped
- stable/2026-07-01/support.json (+ examples): regenerated via tsp compile

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

* Support: make ClassifyProblems articleId optional-only (drop nullable)

Per ARM API best practices (and @azure-tools/typespec-azure-core/no-nullable),
the service omits articleId when no article is available rather than returning
an explicit null, so the property no longer needs to be nullable.

- models.tsp: articleId?: string | null -> articleId?: string; remove the
  no-nullable suppression; update description (omitted instead of null/omitted)
- stable/2026-07-01/support.json: regenerated (x-nullable removed)

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

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Regenerate OpenAPI for DevCenter and Maps after removing armCommonDefinition

The @armCommonDefinition decorators for CustomerManagedKeyEncryption and
Encryption types have been removed in the typespec-azure-resource-manager
package. Add clientName decorators to strip namespace qualification from
emitted type names. Rename local DevCenter KeyEncryptionKeyIdentity model
to KeyEncryptionKeyIdentityUpdate to avoid name clash.

Depends on: Azure/typespec-azure#4627

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

* Avoid incompatible types for existing clients

* Erase changes from existing sdks

* Completely remove additional renames from existing clients

* old package lock

* Updating version for fix

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add VmAllocationInfo model and update ResourceOperation for flexible VM allocation

* Remove obsolete example JSON files for Virtual Machine Bulk Operations and update readme to reflect the new package version.

* add new changes

* update examples

* update model

* add missing endpoints

* add known suppresisons

* add suppression for ResourceProvisionVdiPayload

* update readme based on PR comments

* address comments and add suppression

* update client.tsp file

* rename VmAllocationInfo to VmInfo and update documentation for virtual machine allocation details

* Rename VmInfo model to VirtualMachineInfo and update references in ResourceOperation

* Added minCapacity check for FlexProperties to validate and reject the calls if capacity is not available.

* fix failing tsv check

* remove faulty example info

* Add bulk operation errors list/ack TypeSpec for Microsoft.Compute/Bulkactions 2026-07-06-preview

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

* add new endpoint and fix examples

* address lintdiff errors

* update paths

* add lookbackInMinutes for listBulkOperationErrors

* fix lintdiff issues

* fix lintdiff errors

* add suppression

* fix python sdk failures

* Add service directory for Python SDK generation

* Apply suggestion from @msyyc

---------

Co-authored-by: Asif Mammadov <asifmammadov@microsoft.com>
Co-authored-by: Sumedh Sandeep Parvatikar <sparvatikar@microsoft.com>
Co-authored-by: Asif Mammadov <mammadovwork@gmail.com>
Co-authored-by: Haojing Lu <haojinglu@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Yuchao Yan <yuchaoyan@microsoft.com>
…44452)

* Update emitter output directory in tspconfig.yaml

* Apply suggestion from @kazrael2119
…-mgmt-elastic (#44454)

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

Co-authored-by: Abhinandan Mohan Raj <abmohanr@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add exact C# names for management enum members

Use exact C# client names for management-plane enum values that previously required SDK-side CodeGenMember customizations.

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

* Pin C# API versions for enum rename migration

Keep C# generation on the existing SDK API versions while moving enum member names into TypeSpec.

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

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Remove unnecessary HDInsight C# scope suppressions

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

* Format HDInsight client customization

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

---------

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

* Update client.tsp

* Update client.tsp
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.