Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Nov 13, 2025

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:
    • SDK generation for existing TypeSpec project at specification/managednetworkfabric/ManagedNetworkFabric.ResourceManager.Management for API version 2024-06-15-preview

Summary

Automated SDK generation for ManagedNetworkFabric TypeSpec specification (API version 2024-06-15-preview). Part of release plan 1972, work item 29211.

SDK Generation Results

Successfully generated SDKs for 4/5 languages:

Language Status SDK Pull Request Package Name
JavaScript azure-sdk-for-js#36578 @azure/arm-managednetworkfabric
Java azure-sdk-for-java#47267 azure-resourcemanager-managednetworkfabric
Go azure-sdk-for-go#25615 armmanagednetworkfabric
Python azure-sdk-for-python#44004 azure-mgmt-managednetworkfabric
.NET Build 5569110 failed Requires investigation

Actions Taken

  • Initiated SDK generation pipelines for all requested languages
  • Linked SDK PRs to release plan 1972 and work item 29211
  • Updated SDK package details in release plan
  • Documented .NET failure requiring separate regeneration

.NET SDK Note

Pipeline 5569110 failed. Service team must investigate logs and regenerate separately.

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.
Original prompt

This section details on the original issue you should resolve

<issue_title>[TypeSpec] Generate SDK for TypeSpec project /specification/managednetworkfabric/ManagedNetworkFabric.ResourceManager.Management</issue_title>
<issue_description>## SDK generate request for TypeSpec project
/specification/managednetworkfabric/ManagedNetworkFabric.ResourceManager.Management

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

Release Plan: 1972
TypeSpec project path: ~/specification/managednetworkfabric/ManagedNetworkFabric.ResourceManager.Management
API spec pull request link: #38359
SDK release type: Beta
API spec version: 2024-06-15-preview
Spec Type: TypeSpec
Language: JavaScript,Java,.NET,Go,Python
Release plan work item ID: 29211

Contacts:
nafizhaider

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)


💡 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
Copy link

github-actions bot commented Nov 13, 2025

Next Steps to Merge

⌛ Please wait. Next steps to merge this PR are being evaluated by automation. ⌛

Comment generated by summarize-checks workflow run.

Copilot AI changed the title [WIP] Generate SDK for TypeSpec project ManagedNetworkFabric Generate SDKs for ManagedNetworkFabric TypeSpec (API 2024-06-15-preview) Nov 13, 2025
Copilot AI requested a review from azure-sdk November 13, 2025 18:01
Copilot finished work on behalf of azure-sdk November 13, 2025 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[TypeSpec] Generate SDK for TypeSpec project ~/specification/managednetworkfabric/ManagedNetworkFabric.ResourceManager.Management

2 participants