SDK Generation for DnsResolver TypeSpec Project - 2025-10-01-preview API

[Copilot]

Overview

This PR tracks the SDK generation process for the DnsResolver TypeSpec project at specification/dnsresolver/resource-manager/Microsoft.Network/DnsResolver for the 2025-10-01-preview API version.

What was done

This automated SDK generation workflow was executed as part of Release Plan #1909 (Work Item ID: 28645) linked to API spec PR #37724.

SDK Generation Results

The following SDKs were generated from the TypeSpec specification:

✅ Successfully Generated (3/5):

1. Python (azure-mgmt-dnsresolver)

   • Pull Request: [AutoPR azure-mgmt-dnsresolver]-generated-from-SDK Generation - Python-5425117 azure-sdk-for-python#43279
   • Pipeline: Build 5425117

2. Java (azure-resourcemanager-dnsresolver)

   • Pull Request: [AutoPR azure-resourcemanager-dnsresolver]-generated-from-SDK Generation - Java-5425115 azure-sdk-for-java#46924
   • Pipeline: Build 5425115

3. Go (sdk/resourcemanager/dnsresolver/armdnsresolver)

   • Pull Request: [AutoPR sdk-resourcemanager/dnsresolver/armdnsresolver]-generated-from-SDK Generation - Go-5425116 azure-sdk-for-go#25371
   • Pipeline: Build 5425116

❌ Failed (2/5):

1. .NET (Azure.ResourceManager.DnsResolver)

   • Initial Pipeline: Build 5425118 - Failed
   • Retry Pipeline 1: Build 5509608 - Failed
   • Retry Pipeline 2: Build 5536473 - Failed
   • Retry Pipeline 3 (after main merge): Build 5536518 - Failed
   • Status: Failed (4 attempts) - requires SDK team investigation

2. JavaScript (@azure/arm-dnsresolver)

   • Initial Pipeline: Build 5425113 - Succeeded (PR [botservice] Modify the optionality of 'location' #36130 has git conflicts)
   • Retry Pipeline: Build 5509685 - Failed
   • Status: Failed on regeneration - original PR has git conflicts that need manual resolution

Actions Taken

• ✅ Validated TypeSpec project compilation
• ✅ Retrieved and validated Release Plan 1909
• ✅ Extracted SDK package details from tspconfig.yaml
• ✅ Updated SDK details in the release plan work item
• ✅ Initiated SDK generation pipelines for all 5 languages
• ✅ Monitored pipeline execution to completion
• ✅ Linked all successful SDK PRs to Release Plan 1909
• ✅ Attempted .NET SDK regeneration (Build 5509608) - failed again
• ✅ Attempted JavaScript SDK regeneration (Build 5509685) - failed
• ✅ Attempted .NET SDK regeneration (Build 5536473) - failed third time
• ✅ Attempted .NET SDK regeneration after main merge (Build 5536518) - failed fourth time

Important Notes

• SDKs will NOT be released automatically - As per the request, SDKs will be released later by the service owner (@jamesvoong)
• All successful SDK PRs are in draft state. Move them to Ready for review to start the require approval before merging
• The .NET SDK generation has failed 4 times consecutively (including after merging main branch fix) and requires investigation by the SDK team to determine the root cause (possible TypeSpec configuration issues, build environment problems, or service-specific code generation errors)
• The JavaScript SDK initially succeeded but the PR ([botservice] Modify the optionality of 'location' #36130) has git conflicts. Regeneration attempt also failed - manual resolution may be required
• SDK Release Type: Beta (for preview API version)

Related Links

• Release Plan: https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=61053214-6a8e-f011-b4cc-0022480bb79b
• API Spec PR: Add 2025-10-01-preview changes to dns resolver #37724
• Work Item: 28645

cc: @jamesvoong

---

💡 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

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

Comment generated by summarize-checks workflow run.

[jamesvoongms]

@copilot What is the status of SDK generation?

[Copilot]

@copilot What is the status of SDK generation?

SDK Generation Status Summary

Overall Status: 4/5 Languages Completed Successfully ✅

✅ Successfully Generated SDKs:

1. JavaScript - PR #36130

   • Package: @azure/arm-dnsresolver
   • Status: SDK PR created and linked to Release Plan 1909

2. Python - PR #43279

   • Package: azure-mgmt-dnsresolver
   • Status: SDK PR created and linked to Release Plan 1909

3. Java - PR #46924

   • Package: azure-resourcemanager-dnsresolver
   • Status: SDK PR created and linked to Release Plan 1909

4. Go - PR #25371

   • Package: sdk/resourcemanager/dnsresolver/armdnsresolver
   • Status: SDK PR created and linked to Release Plan 1909

❌ Failed SDK Generation:

1. .NET - Build #5425118
   • Package: Azure.ResourceManager.DnsResolver
   • Status: Pipeline failed - requires investigation and retry

Next Steps:

• The 4 successful SDK PRs are ready for review
• The .NET SDK generation needs to be investigated and regenerated
• All SDK PRs are linked to Release Plan 1909 (Work Item 28645)
• Remember: SDKs should not be released until ready (as per original request)

[jamesvoongms]

@copilot Regenerate SDK

[Copilot]

@copilot Regenerate SDK

I can regenerate the SDK for you. Could you please clarify:

• Do you want to regenerate only the .NET SDK (which failed)?
• Or do you want to regenerate all 5 languages (JavaScript, .NET, Java, Python, Go)?

Please let me know which option you prefer.

[jamesvoongms]

@copilot , please only regenerate the .NET SDK , thank you

[Copilot]

@copilot , please only regenerate the .NET SDK , thank you

I've initiated a new .NET SDK generation pipeline, but unfortunately it has failed again.

Pipeline Details:

• Build ID: 5509608
• Pipeline: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5509608
• Status: Failed

Recommendation:
The .NET SDK generation is failing consistently. This requires investigation by the SDK team to determine the root cause. Possible issues could be:

• TypeSpec configuration issues specific to .NET emitter
• Build environment or dependency problems
• Service-specific code generation errors

Please review the pipeline logs at the link above for detailed error information. The SDK team may need to investigate the tspconfig.yaml .NET emitter configuration or the TypeSpec specification itself.

[jamesvoongms]

@copilot can you also regenerate the javascript SDK ? It seems to have git conflict issues

[Copilot]

@copilot can you also regenerate the javascript SDK ? It seems to have git conflict issues

I've initiated a new JavaScript SDK generation pipeline to resolve the git conflict issues, but unfortunately it has failed.

Pipeline Details:

• Build ID: 5509685
• Pipeline: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5509685
• Status: Failed

The pipeline failure may be related to the git conflict issues you mentioned or other underlying problems. Please review the pipeline logs for detailed error information. The SDK team may need to:

1. Manually resolve the git conflicts in the original PR ([botservice] Modify the optionality of 'location' #36130)
2. Investigate the root cause of the generation failure
3. Update the TypeSpec configuration if needed

[jamesvoongms]

@copilot , can you try regenerating the C# sdk again?

[Copilot]

@copilot , can you try regenerating the C# sdk again?

I've initiated another .NET SDK generation pipeline, but unfortunately it has failed again.

Pipeline Details:

• Build ID: 5536473
• Pipeline: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5536473
• Status: Failed

This is the third attempt at generating the .NET SDK, and all have failed. This indicates a persistent issue that requires deeper investigation by the .NET SDK team. The problem is likely related to:

• TypeSpec to C# code generation issues
• Breaking changes in the TypeSpec specification
• .NET emitter configuration problems in tspconfig.yaml

I recommend filing an issue with the .NET SDK team with the pipeline logs to get this resolved.

[jamesvoongms]

@copilot Copilot, can you try the regeneration about, I have merged main into the branch which should have a fix

[Copilot]

@copilot Copilot, can you try the regeneration about, I have merged main into the branch which should have a fix

I've initiated another .NET SDK generation pipeline after your main branch merge, but unfortunately it has failed again.

Pipeline Details:

• Build ID: 5536518
• Pipeline: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5536518
• Status: Failed

This is now the fourth failed attempt. Despite merging main (which you mentioned should have a fix), the generation is still failing. Please review the pipeline logs to see if:

1. The fix from main was successfully applied
2. There are new/different errors compared to previous attempts
3. Additional configuration changes are needed in the TypeSpec project

The consistent failures suggest a fundamental compatibility issue between the TypeSpec specification and the .NET SDK generator that may require manual intervention.