Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scripts: Stream API for storedProcedure and trigger CRUD #4951

Open
kirankumarkolli opened this issue Jan 7, 2025 · 1 comment · May be fixed by #4978
Open

Scripts: Stream API for storedProcedure and trigger CRUD #4951

kirankumarkolli opened this issue Jan 7, 2025 · 1 comment · May be fixed by #4978
Assignees

Comments

@kirankumarkolli
Copy link
Member

kirankumarkolli commented Jan 7, 2025

Scripts: Stream API for storedProcedure and trigger CRUD

ref: https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/Microsoft.Azure.Cosmos/src/Resource/Scripts/Scripts.cs

@NaluTripician
Copy link
Contributor

Stream APIs for StoredProcedure and Trigger CRUD

Introduction

This document describes the design of the Stream APIs for StoredProcedure and Trigger CRUD. The Stream APIs are used to create, read, update, and delete stored procedures and triggers in a Cosmos DB account. This will also include user-defined functions.

APIs to Be Implemented

The following APIs will be implemented:

  • CreateStoredProcedureStreamAsync
  • ReadStoredProcedureStreamAsync
  • ReplaceStoredProcedureStreamAsync
  • DeleteStoredProcedureStreamAsync
  • CreateTriggerStreamAsync
  • ReadTriggerStreamAsync
  • ReplaceTriggerStreamAsync
  • DeleteTriggerStreamAsync
  • CreateUserDefinedFunctionStreamAsync
  • ReadUserDefinedFunctionStreamAsync
  • ReplaceUserDefinedFunctionStreamAsync
  • DeleteUserDefinedFunctionStreamAsync

Testing

To test the Stream APIs, we will create a test suite that covers all the scenarios of the exisiting non-stream APIs. We will also test the Stream APIs with different types of stored procedures, triggers, and user-defined functions.

@NaluTripician NaluTripician linked a pull request Jan 23, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

2 participants