Provisioning RegenSdkLocal script deletes tspconfig.yaml, losing emitter options

[ArcturusZhang]

Problem

The provisioning \Invoke-SdkRegeneration.ps1\ script deletes \ spconfig.yaml\ from the fetched spec directory (line 175) to avoid linter rules that require packages not in the local
ode_modules. It then manually reconstructs emitter options via --option\ flags.

This is inconsistent with the mgmt \Invoke-SdkRegeneration.ps1, which keeps \ spconfig.yaml\ in place and lets \ sp compile\ read options naturally. The mgmt script only removes \package.json.

Impact

• Options set in \ spconfig.yaml\ (e.g. \�pi-version,
  amespace, etc.) were silently dropped until a manual extraction workaround was added.
• Any new options added to the spec's \ spconfig.yaml\ for the provisioning emitter need to be explicitly forwarded in the script — easy to miss.

Current Workaround

The script now reads all provisioning emitter options from \ spconfig.yaml\ before deleting it and forwards them as --option\ flags. This works but is fragile.

Ideal Fix

Align with the mgmt script approach: keep \ spconfig.yaml\ but strip the \linter\ section (or the \�xtends\ within it) to avoid the linter dependency issue, rather than deleting the entire file.

Related Files

• \�ng/packages/http-client-csharp-provisioning/eng/scripts/Invoke-SdkRegeneration.ps1\ (provisioning — deletes tspconfig)
• \�ng/packages/http-client-csharp-mgmt/eng/scripts/Invoke-SdkRegeneration.ps1\ (mgmt — keeps tspconfig)

[github-actions]

🎯 Agentic Issue Triage

Summary: The Invoke-SdkRegeneration.ps1 script in eng/packages/http-client-csharp-provisioning deletes tspconfig.yaml from the fetched spec directory to bypass linter dependency issues, then manually reconstructs emitter options via --option flags. This is fragile and inconsistent with the mgmt script approach (which keeps tspconfig.yaml and only removes package.json).

📋 Issue Analysis

Root Cause:
The provisioning regen script removes the entire tspconfig.yaml to avoid linter rules that require packages not present in node_modules. As a result, any emitter options in tspconfig.yaml (e.g., api-version, namespace) are silently dropped unless the script explicitly re-forwards them as --option flags.

Impact:

• New emitter options added to a spec's tspconfig.yaml must be manually plumbed through the script — an easy-to-miss failure mode.
• The current workaround (reading all provisioning emitter options before deletion) works but is brittle and adds maintenance burden.

Proposed Fix:
Rather than deleting tspconfig.yaml, selectively strip the linter section (or the $extends within it) so linter-only dependencies are removed while all emitter options are preserved. This aligns with the mgmt script's pattern of only removing package.json.

🔧 Suggested Implementation Approach

1. In Invoke-SdkRegeneration.ps1 (provisioning), instead of deleting tspconfig.yaml:
   • Read the file as YAML/JSON
   • Remove the linter key (or just the $extends within it that pulls in the problematic package)
   • Write the modified content back to the file
2. Remove the manual option extraction / forwarding workaround
3. Verify the approach matches what eng/packages/http-client-csharp-mgmt/eng/scripts/Invoke-SdkRegeneration.ps1 does for tspconfig.yaml

Files to modify:

• eng/packages/http-client-csharp-provisioning/eng/scripts/Invoke-SdkRegeneration.ps1 (line ~175)

🔗 Related Issues

• #56738 – Provisioning Generator tracking issue
• #56747 – AppConfiguration migration tracker

Generated by Agentic Triage for issue #57104 · ◷