SDK Generation for Contoso.Management TypeSpec Project

[Copilot]

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

SDK generation automation for TypeSpec project specification/contosowidgetmanager/Contoso.Management targeting API version 2025-11-01-preview (beta release).

• 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:
  • SDK generation pipeline execution for existing TypeSpec specification. No specification changes.

SDK Generation Results

Configured release plan work item 32756 with package names and triggered generation pipelines for five languages:

Language	Status	Pipeline	Pull Request
.NET	✅ Succeeded	Build 5881023	azure-sdk-for-net#56276
Python	✅ Succeeded	Build 5881024	azure-sdk-for-python#45192
Java	✅ Succeeded	Build 5881022	azure-sdk-for-java#48011
Go	✅ Succeeded	Build 5881021	azure-sdk-for-go#26027
JavaScript	❌ Failed	Build 5881025	Generation failed - requires investigation

Package Names

• .NET: Azure.ResourceManager.Contoso
• Python: azure-mgmt-contoso
• Java: azure-resourcemanager-contoso
• Go: sdk/resourcemanager/contoso/armcontoso
• JavaScript: @azure/arm-contoso

Outstanding Items

• JavaScript SDK generation failed. Pipeline logs indicate TypeSpec compilation or emitter issues requiring resolution before retry.
• All generated PRs remain in draft status pending service owner review.
• SDK release deferred per service owner directive in issue #32756.

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. Release plan 516 updated with SDK generation status.

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.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[TypeSpec] Generate SDK for TypeSpec project specification/contosowidgetmanager/Contoso.Management</issue_title>
<issue_description>## SDK generate request for TypeSpec project specification/contosowidgetmanager/Contoso.Management

Request to generate SDK by Copilot. Do not release SDK
SDK will be released later by service owner.

Release Plan: 516
TypeSpec project path: specification/contosowidgetmanager/Contoso.Management
API spec pull request link: #35573
SDK release type: Beta
API spec version: 2025-11-01-preview
Spec Type: TypeSpec
Language: JavaScript,.NET,Python,Go,Java
Release plan work item ID: 32756

Contacts:
prmarott

Comments:
Generate SDK using Github copilot

Generate SDK for the TypeSpec project and update the generated SDK details in the release plan using release plan work item. Generate a summary and update it back in the linked GitHub issue once SDK pull requests are generated.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [TypeSpec] Generate SDK for TypeSpec project specification/contosowidgetmanager/Contoso.Management #40454

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[github-actions]

Next Steps to Merge

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 Swagger PrettierCheck 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.