Skip to content

Add .NET management emitter to Authorization tspconfig.yaml#42261

Open
jruttle wants to merge 1 commit intoAzure:mainfrom
jruttle:jruttle/add-dotnet-emitter-authorization
Open

Add .NET management emitter to Authorization tspconfig.yaml#42261
jruttle wants to merge 1 commit intoAzure:mainfrom
jruttle:jruttle/add-dotnet-emitter-authorization

Conversation

@jruttle
Copy link
Copy Markdown
Contributor

@jruttle jruttle commented Apr 10, 2026

Summary

Add the @azure-typespec/http-client-csharp-mgmt emitter configuration to the Authorization tspconfig.yaml. This is the only missing language emitter - Python, Java, TypeScript, and Go are already configured.

Motivation

The .NET SDK generation pipeline (7412) ran successfully after the TypeSpec PR (#41617) merged, but produced no changes because the tspconfig.yaml was missing the .NET emitter. This blocked auto-generation of the Azure.ResourceManager.Authorization NuGet package with deny assignment CRUD support.

All four other SDKs have been successfully generated:

Changes

  • Added @azure-typespec/http-client-csharp-mgmt emitter with:
    • namespace: "Azure.ResourceManager.Authorization"
    • emitter-output-dir: "{output-dir}/{service-dir}/{namespace}"

This matches the pattern used by other management plane services (e.g., Microsoft.Advisor, Microsoft.Batch, Microsoft.AppConfiguration).

Checklist

Add @azure-typespec/http-client-csharp-mgmt emitter configuration to enable
.NET SDK generation for Microsoft.Authorization. The other four language
emitters (Python, Java, TypeScript, Go) are already present — .NET was the
only one missing, which blocked .NET SDK auto-generation.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 10, 2026

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.

@github-actions github-actions Bot added ARMReview resource-manager TypeSpec Authored with TypeSpec WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Apr 10, 2026
@jruttle jruttle added Approved-Avocado PublishToCustomers Acknowledgement the changes will be published to Azure customers. labels Apr 10, 2026
@jruttle
Copy link
Copy Markdown
Contributor Author

jruttle commented Apr 10, 2026

ARM Review Request — Config-only change

This PR makes a minimal config-only change — it adds 3 lines to tspconfig.yaml to include the .NET management emitter (@azure-typespec/http-client-csharp-mgmt). There are no API spec changes, no new operations, no schema changes.

Context

The Authorization tspconfig.yaml already has emitters configured for Python, Java, TypeScript, and Go. The .NET emitter was the only one missing, which blocked .NET SDK auto-generation for the deny assignment CRUD operations that shipped in PR #41104 (merged 28 March, ARM signed off by gary-x-li).

All 4 other SDK PRs have been successfully created from the existing tspconfig:

  • Python: azure-sdk-for-python#46223 ✅
  • Go: azure-sdk-for-go#26544 ✅
  • JavaScript: azure-sdk-for-js#38079 ✅
  • Java: azure-sdk-for-java#48751 ✅

Avocado

Added Approved-Avocado label — the MULTIPLE_API_VERSION error is pre-existing in the package-2025-12-01-preview tag (same issue from PR #41104, which was approved and merged).

Could this get expedited ARM sign-off given it's purely an SDK emitter config addition with no API surface changes? Thank you!

@github-actions github-actions Bot added ARMAutoSignedOff-Trivial ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Apr 10, 2026
@jruttle
Copy link
Copy Markdown
Contributor Author

jruttle commented Apr 10, 2026

/merge

@jruttle
Copy link
Copy Markdown
Contributor Author

jruttle commented Apr 13, 2026

Hi @ArthurMa1978 @darshanhs90 — this is a 3-line config-only change adding the .NET management emitter to the Authorization tspconfig.yaml (the only missing language emitter). All checks are passing and the ARMSignedOff label is already applied. Could one of you approve so the /merge can go through? Thanks!

@jruttle
Copy link
Copy Markdown
Contributor Author

jruttle commented Apr 17, 2026

Hi @ArthurMa1978 @darshanhs90 — following up on this PR. It's a 3-line config-only change adding the .NET management emitter to the Authorization tspconfig.yaml — no API spec changes at all. The ARMSignedOff label is already applied.

The Avocado check failure is a pre-existing MULTIPLE_API_VERSION issue in the package-2025-12-01-preview tag (same as in the original PR #41104 which was approved and merged). The Approved-Avocado label has been applied to override this.

@iliu816 — could one of you approve so the /merge can proceed? This is blocking .NET SDK generation for the deny assignment feature. Thanks! 🙏

@iliu816
Copy link
Copy Markdown
Member

iliu816 commented Apr 17, 2026

@jruttle I'm not a code owner for Authorization. It seems like this request should go to @darshanhs90 according to

/specification/authorization/ @darshanhs90

@jruttle
Copy link
Copy Markdown
Contributor Author

jruttle commented Apr 20, 2026

Thanks @iliu816 for pointing that out — really appreciate the help! 🙏

@darshanhs90 — could you take a look at this PR when you get a chance? It's a 3-line config-only change adding the .NET management emitter to the Authorization tspconfig.yaml (no API spec changes). The ARMSignedOff label is already applied and I've run /merge — just needs one approving review. Thanks!

@jruttle jruttle requested a review from mcgallan April 27, 2026 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved-Avocado ARMAutoSignedOff-Trivial ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review Authorization PublishToCustomers Acknowledgement the changes will be published to Azure customers. resource-manager TypeSpec Authored with TypeSpec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants