[Feature request] http-server-csharp: Configuration key to turn of generating Operations controller

[abatishchev]

Clear and concise description of the problem

My RP is behind RPaaS so doesn't need its own Operations controllers, RPaaS will handle it for me.

I'd like to have an option to disable generating it altogether.

Checklist

• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[github-actions]

🎯 Issue Triage

Feature request to add a configuration option to the http-server-csharp emitter to disable generating the Operations controller, useful for RPs behind RPaaS where the platform handles operations automatically.

Category: Feature Request
Area: emitter:service:csharp

🔍 Analysis

• The request targets the http-server-csharp emitter (service-side C# code generation).
• The user's RP is behind RPaaS (Resource Provider as a Service), which provides a built-in Operations endpoint — making a generated OperationsController redundant or conflicting.
• A new emitter configuration key (e.g., generateOperationsController: false) would allow users to opt out of generating this controller.
• No strong duplicate found.

📝 Suggested next steps

• Determine the scope: should this be a per-namespace decorator or an emitter-level config option?
• Identify where OperationsController is generated in the http-server-csharp package and add a flag to skip it.
• Add documentation and tests for the new option.

Generated by Agentic Triage