Updating stable release branch#41047
Open
jeremyfrosti wants to merge 2540 commits into
Open
Conversation
Next Steps to MergeNext steps that must be taken to merge this PR:
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:
Comment generated by summarize-checks workflow run. |
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:
For more information about GitHub Code Scanning, check out the documentation. |
* mitigate breaking change for kusto * update * Revert "update" This reverts commit 174cc99.
…Version: 2026-05-01 (#42428)
…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>
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection 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!
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:
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 ApiViewcomment 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
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.