[Provisioning Generator] dotnet build /t:GenerateCode fails due to missing transitive dependency

[ArcturusZhang]

Description

dotnet build /t:GenerateCode fails for provisioning SDK packages (e.g., Azure.Provisioning.KeyVault) because the published provisioning emitter package is missing @azure-tools/typespec-azure-resource-manager as a dependency.

Error

Cannot find package '@azure-tools/typespec-azure-resource-manager' imported from
.../node_modules/@azure-typespec/http-client-csharp-mgmt/dist/emitter/resolve-arm-resources-converter.js

Followed by TypeSpec compilation errors (Unknown identifier ResourceNameParameter, Unknown decorator @armResourceOperations, etc.)

Root Cause

The provisioning emitter package.json (eng/azure-typespec-http-client-csharp-provisioning-emitter-package.json) only declares:

{
  "dependencies": {
    "@azure-typespec/http-client-csharp-provisioning": "1.0.0-alpha.20260316.3"
  }
}

The provisioning emitter transitively depends on @azure-typespec/http-client-csharp-mgmt, which imports @azure-tools/typespec-azure-resource-manager in resolve-arm-resources-converter.js. However, this transitive dependency is not resolved when tsp-client update runs npm ci in the TempTypeSpecFiles directory.

Workaround

Use RegenSdkLocal.ps1 instead of dotnet build /t:GenerateCode:

pwsh eng/packages/http-client-csharp-provisioning/eng/scripts/RegenSdkLocal.ps1 -Services "KeyVault"

This works because it builds the emitter locally with all dependencies available.

Expected Behavior

dotnet build /t:GenerateCode should work for provisioning SDK packages, just as it works for management SDK packages.

Found In

Provisioning Migration - KeyVault (#56820)

[github-actions]

🎯 Agentic Issue Triage

Summary: The provisioning emitter package (eng/azure-typespec-http-client-csharp-provisioning-emitter-package.json) is missing @azure-tools/typespec-azure-resource-manager as an explicit (transitive) dependency, causing dotnet build /t:GenerateCode to fail for Azure.Provisioning.* packages.

Root Cause Analysis

The dependency chain is:

`@azure-typespec/http-client-csharp-provisioning`
  └── `@azure-typespec/http-client-csharp-mgmt`
        └── `@azure-tools/typespec-azure-resource-manager`  ← not declared in provisioning emitter package.json

When tsp-client update runs npm ci in TempTypeSpecFiles using the provisioning emitter package.json, only the explicitly declared dependencies (and their lock file) are installed. Transitive packages pulled by http-client-csharp-mgmt are not automatically included unless npm ci resolves them through the lock file or they are explicitly declared.

Suggested Fix

Add @azure-tools/typespec-azure-resource-manager as an explicit dependency in eng/azure-typespec-http-client-csharp-provisioning-emitter-package.json:

{
  "dependencies": {
    "`@azure-typespec/http-client-csharp-provisioning`": "1.0.0-alpha.20260316.3",
    "`@azure-tools/typespec-azure-resource-manager`": "(version matching what http-client-csharp-mgmt requires)"
  }
}

Alternatively, ensure the provisioning emitter package's lock file (eng/azure-typespec-http-client-csharp-provisioning-emitter-package-lock.json) includes the transitive dependency so npm ci can install it.

This aligns with how the management emitter package handles its dependencies and would make dotnet build /t:GenerateCode work consistently for provisioning packages.

Workaround

Use RegenSdkLocal.ps1 instead of dotnet build /t:GenerateCode:

pwsh eng/packages/http-client-csharp-provisioning/eng/scripts/RegenSdkLocal.ps1 -Services "KeyVault"

Relevant Files

• eng/azure-typespec-http-client-csharp-provisioning-emitter-package.json — provisioning emitter dependency file
• eng/packages/http-client-csharp-provisioning/ — provisioning generator source
• Related issue: Provisioning Migration - KeyVault #56820 (Provisioning Migration - KeyVault)

Generated by Agentic Triage for issue #57165 · ◷