UNPKG

8.74 kBTypeScriptView Raw
1// Copyright (c) .NET Foundation. All rights reserved.
2// Licensed under the MIT License.
3
4import { FunctionInput, FunctionOptions, FunctionOutput, FunctionResult, FunctionTrigger, RetryOptions } from './index';
5import { InvocationContext } from './InvocationContext';
6
7export type CosmosDBv3Handler = (documents: unknown[], context: InvocationContext) => FunctionResult;
8
9export interface CosmosDBv3FunctionOptions extends CosmosDBv3TriggerOptions, Partial<FunctionOptions> {
10 handler: CosmosDBv3Handler;
11
12 trigger?: CosmosDBv3Trigger;
13
14 /**
15 * An optional retry policy to rerun a failed execution until either successful completion occurs or the maximum number of retries is reached.
16 * Learn more [here](https://learn.microsoft.com/azure/azure-functions/functions-bindings-error-pages)
17 */
18 retry?: RetryOptions;
19}
20
21export interface CosmosDBv3InputOptions {
22 /**
23 * An app setting (or environment variable) with the Cosmos DB connection string
24 */
25 connectionStringSetting: string;
26
27 /**
28 * The name of the Azure Cosmos DB database with the collection being monitored
29 */
30 databaseName: string;
31
32 /**
33 * The name of the collection being monitored
34 */
35 collectionName: string;
36
37 /**
38 * Specifies the partition key value for the lookup. May include binding parameters. It is required for lookups in partitioned collections
39 */
40 partitionKey?: string;
41
42 /**
43 * The ID of the document to retrieve. This property supports [binding expressions](https://docs.microsoft.com/azure/azure-functions/functions-bindings-expressions-patterns).
44 * Don't set both the id and sqlQuery properties. If you don't set either one, the entire collection is retrieved.
45 */
46 id?: string;
47
48 /**
49 * An Azure Cosmos DB SQL query used for retrieving multiple documents. The property supports runtime bindings, as in this example:
50 * `SELECT * FROM c where c.departmentId = {departmentId}`
51 * Don't set both the id and sqlQuery properties. If you don't set either one, the entire collection is retrieved.
52 */
53 sqlQuery?: string;
54
55 /**
56 * Defines preferred locations (regions) for geo-replicated database accounts in the Azure Cosmos DB service.
57 * Values should be comma-separated. For example, East US,South Central US,North Europe
58 */
59 preferredLocations?: string;
60}
61export type CosmosDBv3Input = FunctionInput & CosmosDBv3InputOptions;
62
63export interface CosmosDBv3TriggerOptions {
64 /**
65 * An app setting (or environment variable) with the Cosmos DB connection string
66 */
67 connectionStringSetting: string;
68
69 /**
70 * The name of the Azure Cosmos DB database with the collection being monitored
71 */
72 databaseName: string;
73
74 /**
75 * The name of the collection being monitored
76 */
77 collectionName: string;
78
79 /**
80 * The name of an app setting that contains the connection string to the service which holds the lease collection.
81 * If not set it will connect to the service defined by `connectionStringSetting`
82 */
83 leaseConnectionStringSetting?: string;
84
85 /**
86 * The name of the database that holds the collection to store leases. If not set, it will use the value of `databaseName`
87 */
88 leaseDatabaseName?: string;
89
90 /**
91 * The name of the collection to store leases. If not set, it will use "leases"
92 */
93 leaseCollectionName?: string;
94
95 /**
96 * Checks for existence and automatically creates the leases collection. Default is `false`
97 */
98 createLeaseCollectionIfNotExists?: boolean;
99
100 /**
101 * When `createLeaseCollectionIfNotExists` is set to `true`, defines the amount of Request Units to assign to the created lease collection
102 */
103 leaseCollectionThroughput?: number;
104
105 /**
106 * When set, the value is added as a prefix to the leases created in the Lease collection for this function.
107 * Using a prefix allows two separate Azure Functions to share the same Lease collection by using different prefixes.
108 */
109 leaseCollectionPrefix?: string;
110
111 /**
112 * The time (in milliseconds) for the delay between polling a partition for new changes on the feed, after all current changes are drained.
113 * Default is 5,000 milliseconds, or 5 seconds.
114 */
115 feedPollDelay?: number;
116
117 /**
118 * When set, it defines, in milliseconds, the interval to kick off a task to compute if partitions are distributed evenly among known host instances.
119 * Default is 13000 (13 seconds).
120 */
121 leaseAcquireInterval?: number;
122
123 /**
124 * When set, it defines, in milliseconds, the interval for which the lease is taken on a lease representing a partition.
125 * If the lease is not renewed within this interval, it will cause it to expire and ownership of the partition will move to another instance.
126 * Default is 60000 (60 seconds).
127 */
128 leaseExpirationInterval?: number;
129
130 /**
131 * When set, it defines, in milliseconds, the renew interval for all leases for partitions currently held by an instance.
132 * Default is 17000 (17 seconds).
133 */
134 leaseRenewInterval?: number;
135
136 /**
137 * When set, it defines, in milliseconds, the interval between lease checkpoints. Default is always after each Function call.
138 */
139 checkpointInterval?: number;
140
141 /**
142 * Customizes the amount of documents between lease checkpoints. Default is after every function call.
143 */
144 checkpointDocumentCount?: number;
145
146 /**
147 * When set, this property sets the maximum number of items received per Function call.
148 * If operations in the monitored container are performed through stored procedures, transaction scope is preserved when reading items from the change feed.
149 * As a result, the number of items received could be higher than the specified value so that the items changed by the same transaction are returned as part of one atomic batch.
150 */
151 maxItemsPerInvocation?: number;
152
153 /**
154 * This option tells the Trigger to read changes from the beginning of the container's change history instead of starting at the current time.
155 * Reading from the beginning only works the first time the trigger starts, as in subsequent runs, the checkpoints are already stored.
156 * Setting this option to true when there are leases already created has no effect.
157 */
158 startFromBeginning?: boolean;
159
160 /**
161 * Defines preferred locations (regions) for geo-replicated database accounts in the Azure Cosmos DB service.
162 * Values should be comma-separated. For example, East US,South Central US,North Europe
163 */
164 preferredLocations?: string;
165
166 /**
167 * Enables multi-region accounts for writing to the leases collection.
168 */
169 useMultipleWriteLocations?: boolean;
170}
171export type CosmosDBv3Trigger = FunctionTrigger & CosmosDBv3TriggerOptions;
172
173export interface CosmosDBv3OutputOptions {
174 /**
175 * An app setting (or environment variable) with the Cosmos DB connection string
176 */
177 connectionStringSetting: string;
178
179 /**
180 * The name of the Azure Cosmos DB database with the collection being monitored
181 */
182 databaseName: string;
183
184 /**
185 * The name of the collection being monitored
186 */
187 collectionName: string;
188
189 /**
190 * A boolean value to indicate whether the collection is created when it doesn't exist.
191 * The default is false because new collections are created with reserved throughput, which has cost implications. For more information, see the [pricing page](https://azure.microsoft.com/pricing/details/cosmos-db/).
192 */
193 createIfNotExists?: boolean;
194
195 /**
196 * When `createIfNotExists` is true, it defines the partition key path for the created collection. May include binding parameters.
197 */
198 partitionKey?: string;
199
200 /**
201 * When createIfNotExists is true, it defines the [throughput](https://docs.microsoft.com/azure/cosmos-db/set-throughput) of the created collection
202 */
203 collectionThroughput?: number;
204
205 /**
206 * Defines preferred locations (regions) for geo-replicated database accounts in the Azure Cosmos DB service.
207 * Values should be comma-separated. For example, East US,South Central US,North Europe
208 */
209 preferredLocations?: string;
210
211 /**
212 * When set to true along with preferredLocations, supports multi-region writes in the Azure Cosmos DB service.
213 */
214 useMultipleWriteLocations?: boolean;
215}
216export type CosmosDBv3Output = FunctionOutput & CosmosDBv3OutputOptions;