SDK generation blocked: release plan 35135 missing package metadata for all languages

[aboodasfari]

Hi team,

SDK generation is blocked for a newly created release plan and it looks like a backend metadata indexing issue.

Context

• Release Plan ID: 35135 (Public Preview, management plane)
• TypeSpec project: specification/containerservice/resource-manager/Microsoft.ContainerService/preparedimagespecification
• Spec PR: containerservice: PreparedImageSpecification 2026-02-02-preview API updates azure-rest-api-specs#43365
• Affected languages: .NET, Python, Java, JavaScript, Go

Symptoms

azsdk_run_generate_sdk fails for all 5 languages with:

"Release plan work item with ID 35135 does not have a package name specified for ."

Attempting to backfill from tspconfig.yaml via azsdk_update_sdk_details_in_release_plan returns:

"No valid SDK packages found in the TypeSpec project metadata."

azsdk_get_service_details_by_typespec_path returns:

"No release plan found for TypeSpec project path: specification/containerservice/resource-manager/Microsoft.ContainerService/preparedimagespecification"

Evidence the tspconfig is configured correctly

The TypeSpec project's tspconfig.yaml defines emitter blocks with package metadata for all 5 languages:

Language	Emitter	Package
.NET	@azure-typespec/http-client-csharp-mgmt	Azure.ResourceManager.ContainerServicePreparedImageSpecification
Java	@azure-tools/typespec-java	azure-resourcemanager-containerservice-preparedimgspec
Go	@azure-tools/typespec-go	armcontainerservicepreparedimagespecification
Python	@azure-tools/typespec-python	azure-mgmt-containerservicepreparedimagespecification
JavaScript	@azure-tools/typespec-ts	@azure/arm-containerservicepreparedimagespecification

The phrasing of the error ("No valid SDK packages found in the TypeSpec project metadata") plus the matching "No release plan found for TypeSpec project path …" from azsdk_get_service_details_by_typespec_path suggests the SDK-pipeline-side catalog hasn't indexed this TypeSpec path yet — but happy to be wrong about the cause if it's actually something fixable in the tspconfig.

Ask

Any pointers on how to unblock SDK details population? Happy to provide more diagnostics.

Thanks!

[praveenkuttappan]

@aboodasfari This requires a change in azsdk MCP server side to handle output directory config in the tspconfig and it seems this is the first project in specs repo with global output-dir config.

I have updated the release plan with package names to unblock this release plan and also triggered SDK generation. We will release a fix in azsdk agent to avoid this issue in future.