[P1] Add Stored Procedures, UDFs, and Triggers management

[sajeetharan]

Feature Request

Priority: P1 (High)

Description

Cosmos DB supports server-side programming (stored procedures, UDFs, triggers) but CosmosDB Shell cannot list, create, update, or execute them. Users must leave the shell to manage these resources.

Comparable Features in Other Shells

• mongosh: Server-side JavaScript execution
• sqlcmd: Stored procedure execution via T-SQL

Proposed Behavior

Add commands for server-side programming management:

• sproc list — List stored procedures in current container
• sproc show <name> — Display stored procedure body
• sproc create <name> <file> — Create from a JS file
• sproc exec <name> [params] — Execute a stored procedure
• udf list/show/create/delete — UDF management
• trigger list/show/create/delete — Trigger management

Example Usage

cd /MyDatabase/MyContainer
sproc list
sproc create myProc ./myProc.js
sproc exec myProc '["param1", "param2"]' --partition-key "pk1"
udf list
trigger list

[tnaum-ms]

Good catch. Worth noting though that server-side JavaScript (stored procedures, UDFs, triggers) is not in scope for the DocumentDB shell, since Azure DocumentDB does not support it at the platform level. This is also aligned with MongoDB's own direction: $function, $accumulator, and $where were all deprecated as of version 8.0, and mapReduce was gone even earlier (5.0).

That said, Cosmos DB for NoSQL does still support server-side JavaScript, so for users on that offering, exposing sproc/udf/trigger management via the shell makes sense.

One suggestion worth considering: a minimal built-in editor for interactive users. Rather than exporting a stored procedure body to a file, editing it, and importing it back, an inline editor would let you open, edit, and save it without ever leaving the shell. It would also be simpler to implement than it sounds. File-based commands remain the right path for agentic workflows using the CLI or the MCP server directly, but for someone working interactively at the prompt, the editor experience would be far more natural.

That same editor would pay dividends beyond sprocs too: multi-line queries, pipeline drafting, any scenario where you want to compose something non-trivial without leaving the shell.

[mkrueger]

This is more complex than the other issues I worked on.

Ok I split sproc/udf & triggers. SPROC first. Need to work on the others too.

Subcommand Behavior
sproc list List stored procedures in the current container
sproc show Display a stored procedure body
sproc exists Returns a boolean usable directly in if/while conditions
sproc create Create from a JS file (or piped body); --force to replace
sproc create Create from an external editor
sproc edit Edit the body in an external editor and save back
sproc exec [params] Execute with a JSON array of args and --partition-key
sproc delete Delete a stored procedure

---

I think it's good to have an editor editing that and saving it back when closing it.

Any other ideas/feedback on that?

Builds are here:

https://github.com/Azure/CosmosDBShell/actions/runs/27275831555