@mochabug/adaptkit 0.2.0-alpha.1 → 0.3.0-alpha.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,460 @@
1
+ import type { BinaryWriteOptions } from "@protobuf-ts/runtime";
2
+ import type { IBinaryWriter } from "@protobuf-ts/runtime";
3
+ import type { BinaryReadOptions } from "@protobuf-ts/runtime";
4
+ import type { IBinaryReader } from "@protobuf-ts/runtime";
5
+ import type { PartialMessage } from "@protobuf-ts/runtime";
6
+ import { MessageType } from "@protobuf-ts/runtime";
7
+ /**
8
+ * Defines the HTTP configuration for an API service. It contains a list of
9
+ * [HttpRule][google.api.HttpRule], each specifying the mapping of an RPC method
10
+ * to one or more HTTP REST API methods.
11
+ *
12
+ * @generated from protobuf message google.api.Http
13
+ */
14
+ export interface Http {
15
+ /**
16
+ * A list of HTTP configuration rules that apply to individual API methods.
17
+ *
18
+ * **NOTE:** All service configuration rules follow "last one wins" order.
19
+ *
20
+ * @generated from protobuf field: repeated google.api.HttpRule rules = 1;
21
+ */
22
+ rules: HttpRule[];
23
+ /**
24
+ * When set to true, URL path parameters will be fully URI-decoded except in
25
+ * cases of single segment matches in reserved expansion, where "%2F" will be
26
+ * left encoded.
27
+ *
28
+ * The default behavior is to not decode RFC 6570 reserved characters in multi
29
+ * segment matches.
30
+ *
31
+ * @generated from protobuf field: bool fully_decode_reserved_expansion = 2;
32
+ */
33
+ fullyDecodeReservedExpansion: boolean;
34
+ }
35
+ /**
36
+ * # gRPC Transcoding
37
+ *
38
+ * gRPC Transcoding is a feature for mapping between a gRPC method and one or
39
+ * more HTTP REST endpoints. It allows developers to build a single API service
40
+ * that supports both gRPC APIs and REST APIs. Many systems, including [Google
41
+ * APIs](https://github.com/googleapis/googleapis),
42
+ * [Cloud Endpoints](https://cloud.google.com/endpoints), [gRPC
43
+ * Gateway](https://github.com/grpc-ecosystem/grpc-gateway),
44
+ * and [Envoy](https://github.com/envoyproxy/envoy) proxy support this feature
45
+ * and use it for large scale production services.
46
+ *
47
+ * `HttpRule` defines the schema of the gRPC/REST mapping. The mapping specifies
48
+ * how different portions of the gRPC request message are mapped to the URL
49
+ * path, URL query parameters, and HTTP request body. It also controls how the
50
+ * gRPC response message is mapped to the HTTP response body. `HttpRule` is
51
+ * typically specified as an `google.api.http` annotation on the gRPC method.
52
+ *
53
+ * Each mapping specifies a URL path template and an HTTP method. The path
54
+ * template may refer to one or more fields in the gRPC request message, as long
55
+ * as each field is a non-repeated field with a primitive (non-message) type.
56
+ * The path template controls how fields of the request message are mapped to
57
+ * the URL path.
58
+ *
59
+ * Example:
60
+ *
61
+ * service Messaging {
62
+ * rpc GetMessage(GetMessageRequest) returns (Message) {
63
+ * option (google.api.http) = {
64
+ * get: "/v1/{name=messages/*}"
65
+ * };
66
+ * }
67
+ * }
68
+ * message GetMessageRequest {
69
+ * string name = 1; // Mapped to URL path.
70
+ * }
71
+ * message Message {
72
+ * string text = 1; // The resource content.
73
+ * }
74
+ *
75
+ * This enables an HTTP REST to gRPC mapping as below:
76
+ *
77
+ * HTTP | gRPC
78
+ * -----|-----
79
+ * `GET /v1/messages/123456` | `GetMessage(name: "messages/123456")`
80
+ *
81
+ * Any fields in the request message which are not bound by the path template
82
+ * automatically become HTTP query parameters if there is no HTTP request body.
83
+ * For example:
84
+ *
85
+ * service Messaging {
86
+ * rpc GetMessage(GetMessageRequest) returns (Message) {
87
+ * option (google.api.http) = {
88
+ * get:"/v1/messages/{message_id}"
89
+ * };
90
+ * }
91
+ * }
92
+ * message GetMessageRequest {
93
+ * message SubMessage {
94
+ * string subfield = 1;
95
+ * }
96
+ * string message_id = 1; // Mapped to URL path.
97
+ * int64 revision = 2; // Mapped to URL query parameter `revision`.
98
+ * SubMessage sub = 3; // Mapped to URL query parameter `sub.subfield`.
99
+ * }
100
+ *
101
+ * This enables a HTTP JSON to RPC mapping as below:
102
+ *
103
+ * HTTP | gRPC
104
+ * -----|-----
105
+ * `GET /v1/messages/123456?revision=2&sub.subfield=foo` |
106
+ * `GetMessage(message_id: "123456" revision: 2 sub: SubMessage(subfield:
107
+ * "foo"))`
108
+ *
109
+ * Note that fields which are mapped to URL query parameters must have a
110
+ * primitive type or a repeated primitive type or a non-repeated message type.
111
+ * In the case of a repeated type, the parameter can be repeated in the URL
112
+ * as `...?param=A&param=B`. In the case of a message type, each field of the
113
+ * message is mapped to a separate parameter, such as
114
+ * `...?foo.a=A&foo.b=B&foo.c=C`.
115
+ *
116
+ * For HTTP methods that allow a request body, the `body` field
117
+ * specifies the mapping. Consider a REST update method on the
118
+ * message resource collection:
119
+ *
120
+ * service Messaging {
121
+ * rpc UpdateMessage(UpdateMessageRequest) returns (Message) {
122
+ * option (google.api.http) = {
123
+ * patch: "/v1/messages/{message_id}"
124
+ * body: "message"
125
+ * };
126
+ * }
127
+ * }
128
+ * message UpdateMessageRequest {
129
+ * string message_id = 1; // mapped to the URL
130
+ * Message message = 2; // mapped to the body
131
+ * }
132
+ *
133
+ * The following HTTP JSON to RPC mapping is enabled, where the
134
+ * representation of the JSON in the request body is determined by
135
+ * protos JSON encoding:
136
+ *
137
+ * HTTP | gRPC
138
+ * -----|-----
139
+ * `PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:
140
+ * "123456" message { text: "Hi!" })`
141
+ *
142
+ * The special name `*` can be used in the body mapping to define that
143
+ * every field not bound by the path template should be mapped to the
144
+ * request body. This enables the following alternative definition of
145
+ * the update method:
146
+ *
147
+ * service Messaging {
148
+ * rpc UpdateMessage(Message) returns (Message) {
149
+ * option (google.api.http) = {
150
+ * patch: "/v1/messages/{message_id}"
151
+ * body: "*"
152
+ * };
153
+ * }
154
+ * }
155
+ * message Message {
156
+ * string message_id = 1;
157
+ * string text = 2;
158
+ * }
159
+ *
160
+ *
161
+ * The following HTTP JSON to RPC mapping is enabled:
162
+ *
163
+ * HTTP | gRPC
164
+ * -----|-----
165
+ * `PATCH /v1/messages/123456 { "text": "Hi!" }` | `UpdateMessage(message_id:
166
+ * "123456" text: "Hi!")`
167
+ *
168
+ * Note that when using `*` in the body mapping, it is not possible to
169
+ * have HTTP parameters, as all fields not bound by the path end in
170
+ * the body. This makes this option more rarely used in practice when
171
+ * defining REST APIs. The common usage of `*` is in custom methods
172
+ * which don't use the URL at all for transferring data.
173
+ *
174
+ * It is possible to define multiple HTTP methods for one RPC by using
175
+ * the `additional_bindings` option. Example:
176
+ *
177
+ * service Messaging {
178
+ * rpc GetMessage(GetMessageRequest) returns (Message) {
179
+ * option (google.api.http) = {
180
+ * get: "/v1/messages/{message_id}"
181
+ * additional_bindings {
182
+ * get: "/v1/users/{user_id}/messages/{message_id}"
183
+ * }
184
+ * };
185
+ * }
186
+ * }
187
+ * message GetMessageRequest {
188
+ * string message_id = 1;
189
+ * string user_id = 2;
190
+ * }
191
+ *
192
+ * This enables the following two alternative HTTP JSON to RPC mappings:
193
+ *
194
+ * HTTP | gRPC
195
+ * -----|-----
196
+ * `GET /v1/messages/123456` | `GetMessage(message_id: "123456")`
197
+ * `GET /v1/users/me/messages/123456` | `GetMessage(user_id: "me" message_id:
198
+ * "123456")`
199
+ *
200
+ * ## Rules for HTTP mapping
201
+ *
202
+ * 1. Leaf request fields (recursive expansion nested messages in the request
203
+ * message) are classified into three categories:
204
+ * - Fields referred by the path template. They are passed via the URL path.
205
+ * - Fields referred by the [HttpRule.body][google.api.HttpRule.body]. They
206
+ * are passed via the HTTP
207
+ * request body.
208
+ * - All other fields are passed via the URL query parameters, and the
209
+ * parameter name is the field path in the request message. A repeated
210
+ * field can be represented as multiple query parameters under the same
211
+ * name.
212
+ * 2. If [HttpRule.body][google.api.HttpRule.body] is "*", there is no URL
213
+ * query parameter, all fields
214
+ * are passed via URL path and HTTP request body.
215
+ * 3. If [HttpRule.body][google.api.HttpRule.body] is omitted, there is no HTTP
216
+ * request body, all
217
+ * fields are passed via URL path and URL query parameters.
218
+ *
219
+ * ### Path template syntax
220
+ *
221
+ * Template = "/" Segments [ Verb ] ;
222
+ * Segments = Segment { "/" Segment } ;
223
+ * Segment = "*" | "**" | LITERAL | Variable ;
224
+ * Variable = "{" FieldPath [ "=" Segments ] "}" ;
225
+ * FieldPath = IDENT { "." IDENT } ;
226
+ * Verb = ":" LITERAL ;
227
+ *
228
+ * The syntax `*` matches a single URL path segment. The syntax `**` matches
229
+ * zero or more URL path segments, which must be the last part of the URL path
230
+ * except the `Verb`.
231
+ *
232
+ * The syntax `Variable` matches part of the URL path as specified by its
233
+ * template. A variable template must not contain other variables. If a variable
234
+ * matches a single path segment, its template may be omitted, e.g. `{var}`
235
+ * is equivalent to `{var=*}`.
236
+ *
237
+ * The syntax `LITERAL` matches literal text in the URL path. If the `LITERAL`
238
+ * contains any reserved character, such characters should be percent-encoded
239
+ * before the matching.
240
+ *
241
+ * If a variable contains exactly one path segment, such as `"{var}"` or
242
+ * `"{var=*}"`, when such a variable is expanded into a URL path on the client
243
+ * side, all characters except `[-_.~0-9a-zA-Z]` are percent-encoded. The
244
+ * server side does the reverse decoding. Such variables show up in the
245
+ * [Discovery
246
+ * Document](https://developers.google.com/discovery/v1/reference/apis) as
247
+ * `{var}`.
248
+ *
249
+ * If a variable contains multiple path segments, such as `"{var=foo/*}"`
250
+ * or `"{var=**}"`, when such a variable is expanded into a URL path on the
251
+ * client side, all characters except `[-_.~/0-9a-zA-Z]` are percent-encoded.
252
+ * The server side does the reverse decoding, except "%2F" and "%2f" are left
253
+ * unchanged. Such variables show up in the
254
+ * [Discovery
255
+ * Document](https://developers.google.com/discovery/v1/reference/apis) as
256
+ * `{+var}`.
257
+ *
258
+ * ## Using gRPC API Service Configuration
259
+ *
260
+ * gRPC API Service Configuration (service config) is a configuration language
261
+ * for configuring a gRPC service to become a user-facing product. The
262
+ * service config is simply the YAML representation of the `google.api.Service`
263
+ * proto message.
264
+ *
265
+ * As an alternative to annotating your proto file, you can configure gRPC
266
+ * transcoding in your service config YAML files. You do this by specifying a
267
+ * `HttpRule` that maps the gRPC method to a REST endpoint, achieving the same
268
+ * effect as the proto annotation. This can be particularly useful if you
269
+ * have a proto that is reused in multiple services. Note that any transcoding
270
+ * specified in the service config will override any matching transcoding
271
+ * configuration in the proto.
272
+ *
273
+ * Example:
274
+ *
275
+ * http:
276
+ * rules:
277
+ * # Selects a gRPC method and applies HttpRule to it.
278
+ * - selector: example.v1.Messaging.GetMessage
279
+ * get: /v1/messages/{message_id}/{sub.subfield}
280
+ *
281
+ * ## Special notes
282
+ *
283
+ * When gRPC Transcoding is used to map a gRPC to JSON REST endpoints, the
284
+ * proto to JSON conversion must follow the [proto3
285
+ * specification](https://developers.google.com/protocol-buffers/docs/proto3#json).
286
+ *
287
+ * While the single segment variable follows the semantics of
288
+ * [RFC 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2 Simple String
289
+ * Expansion, the multi segment variable **does not** follow RFC 6570 Section
290
+ * 3.2.3 Reserved Expansion. The reason is that the Reserved Expansion
291
+ * does not expand special characters like `?` and `#`, which would lead
292
+ * to invalid URLs. As the result, gRPC Transcoding uses a custom encoding
293
+ * for multi segment variables.
294
+ *
295
+ * The path variables **must not** refer to any repeated or mapped field,
296
+ * because client libraries are not capable of handling such variable expansion.
297
+ *
298
+ * The path variables **must not** capture the leading "/" character. The reason
299
+ * is that the most common use case "{var}" does not capture the leading "/"
300
+ * character. For consistency, all path variables must share the same behavior.
301
+ *
302
+ * Repeated message fields must not be mapped to URL query parameters, because
303
+ * no client library can support such complicated mapping.
304
+ *
305
+ * If an API needs to use a JSON array for request or response body, it can map
306
+ * the request or response body to a repeated field. However, some gRPC
307
+ * Transcoding implementations may not support this feature.
308
+ *
309
+ * @generated from protobuf message google.api.HttpRule
310
+ */
311
+ export interface HttpRule {
312
+ /**
313
+ * Selects a method to which this rule applies.
314
+ *
315
+ * Refer to [selector][google.api.DocumentationRule.selector] for syntax
316
+ * details.
317
+ *
318
+ * @generated from protobuf field: string selector = 1;
319
+ */
320
+ selector: string;
321
+ /**
322
+ * @generated from protobuf oneof: pattern
323
+ */
324
+ pattern: {
325
+ oneofKind: "get";
326
+ /**
327
+ * Maps to HTTP GET. Used for listing and getting information about
328
+ * resources.
329
+ *
330
+ * @generated from protobuf field: string get = 2;
331
+ */
332
+ get: string;
333
+ } | {
334
+ oneofKind: "put";
335
+ /**
336
+ * Maps to HTTP PUT. Used for replacing a resource.
337
+ *
338
+ * @generated from protobuf field: string put = 3;
339
+ */
340
+ put: string;
341
+ } | {
342
+ oneofKind: "post";
343
+ /**
344
+ * Maps to HTTP POST. Used for creating a resource or performing an action.
345
+ *
346
+ * @generated from protobuf field: string post = 4;
347
+ */
348
+ post: string;
349
+ } | {
350
+ oneofKind: "delete";
351
+ /**
352
+ * Maps to HTTP DELETE. Used for deleting a resource.
353
+ *
354
+ * @generated from protobuf field: string delete = 5;
355
+ */
356
+ delete: string;
357
+ } | {
358
+ oneofKind: "patch";
359
+ /**
360
+ * Maps to HTTP PATCH. Used for updating a resource.
361
+ *
362
+ * @generated from protobuf field: string patch = 6;
363
+ */
364
+ patch: string;
365
+ } | {
366
+ oneofKind: "custom";
367
+ /**
368
+ * The custom pattern is used for specifying an HTTP method that is not
369
+ * included in the `pattern` field, such as HEAD, or "*" to leave the
370
+ * HTTP method unspecified for this rule. The wild-card rule is useful
371
+ * for services that provide content to Web (HTML) clients.
372
+ *
373
+ * @generated from protobuf field: google.api.CustomHttpPattern custom = 8;
374
+ */
375
+ custom: CustomHttpPattern;
376
+ } | {
377
+ oneofKind: undefined;
378
+ };
379
+ /**
380
+ * The name of the request field whose value is mapped to the HTTP request
381
+ * body, or `*` for mapping all request fields not captured by the path
382
+ * pattern to the HTTP body, or omitted for not having any HTTP request body.
383
+ *
384
+ * NOTE: the referred field must be present at the top-level of the request
385
+ * message type.
386
+ *
387
+ * @generated from protobuf field: string body = 7;
388
+ */
389
+ body: string;
390
+ /**
391
+ * Optional. The name of the response field whose value is mapped to the HTTP
392
+ * response body. When omitted, the entire response message will be used
393
+ * as the HTTP response body.
394
+ *
395
+ * NOTE: The referred field must be present at the top-level of the response
396
+ * message type.
397
+ *
398
+ * @generated from protobuf field: string response_body = 12;
399
+ */
400
+ responseBody: string;
401
+ /**
402
+ * Additional HTTP bindings for the selector. Nested bindings must
403
+ * not contain an `additional_bindings` field themselves (that is,
404
+ * the nesting may only be one level deep).
405
+ *
406
+ * @generated from protobuf field: repeated google.api.HttpRule additional_bindings = 11;
407
+ */
408
+ additionalBindings: HttpRule[];
409
+ }
410
+ /**
411
+ * A custom pattern is used for defining custom HTTP verb.
412
+ *
413
+ * @generated from protobuf message google.api.CustomHttpPattern
414
+ */
415
+ export interface CustomHttpPattern {
416
+ /**
417
+ * The name of this custom HTTP verb.
418
+ *
419
+ * @generated from protobuf field: string kind = 1;
420
+ */
421
+ kind: string;
422
+ /**
423
+ * The path matched by this custom verb.
424
+ *
425
+ * @generated from protobuf field: string path = 2;
426
+ */
427
+ path: string;
428
+ }
429
+ declare class Http$Type extends MessageType<Http> {
430
+ constructor();
431
+ create(value?: PartialMessage<Http>): Http;
432
+ internalBinaryRead(reader: IBinaryReader, length: number, options: BinaryReadOptions, target?: Http): Http;
433
+ internalBinaryWrite(message: Http, writer: IBinaryWriter, options: BinaryWriteOptions): IBinaryWriter;
434
+ }
435
+ /**
436
+ * @generated MessageType for protobuf message google.api.Http
437
+ */
438
+ export declare const Http: Http$Type;
439
+ declare class HttpRule$Type extends MessageType<HttpRule> {
440
+ constructor();
441
+ create(value?: PartialMessage<HttpRule>): HttpRule;
442
+ internalBinaryRead(reader: IBinaryReader, length: number, options: BinaryReadOptions, target?: HttpRule): HttpRule;
443
+ internalBinaryWrite(message: HttpRule, writer: IBinaryWriter, options: BinaryWriteOptions): IBinaryWriter;
444
+ }
445
+ /**
446
+ * @generated MessageType for protobuf message google.api.HttpRule
447
+ */
448
+ export declare const HttpRule: HttpRule$Type;
449
+ declare class CustomHttpPattern$Type extends MessageType<CustomHttpPattern> {
450
+ constructor();
451
+ create(value?: PartialMessage<CustomHttpPattern>): CustomHttpPattern;
452
+ internalBinaryRead(reader: IBinaryReader, length: number, options: BinaryReadOptions, target?: CustomHttpPattern): CustomHttpPattern;
453
+ internalBinaryWrite(message: CustomHttpPattern, writer: IBinaryWriter, options: BinaryWriteOptions): IBinaryWriter;
454
+ }
455
+ /**
456
+ * @generated MessageType for protobuf message google.api.CustomHttpPattern
457
+ */
458
+ export declare const CustomHttpPattern: CustomHttpPattern$Type;
459
+ export {};
460
+ //# sourceMappingURL=http.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"http.d.ts","sourceRoot":"","sources":["../../../../src/genproto/google/api/http.ts"],"names":[],"mappings":"AAkBA,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,sBAAsB,CAAC;AAC/D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAE1D,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,sBAAsB,CAAC;AAC9D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAE1D,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,sBAAsB,CAAC;AAG3D,OAAO,EAAE,WAAW,EAAE,MAAM,sBAAsB,CAAC;AACnD;;;;;;GAMG;AACH,MAAM,WAAW,IAAI;IACjB;;;;;;OAMG;IACH,KAAK,EAAE,QAAQ,EAAE,CAAC;IAClB;;;;;;;;;OASG;IACH,4BAA4B,EAAE,OAAO,CAAC;CACzC;AACD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmRG;AACH,MAAM,WAAW,QAAQ;IACrB;;;;;;;OAOG;IACH,QAAQ,EAAE,MAAM,CAAC;IACjB;;OAEG;IACH,OAAO,EAAE;QACL,SAAS,EAAE,KAAK,CAAC;QACjB;;;;;WAKG;QACH,GAAG,EAAE,MAAM,CAAC;KACf,GAAG;QACA,SAAS,EAAE,KAAK,CAAC;QACjB;;;;WAIG;QACH,GAAG,EAAE,MAAM,CAAC;KACf,GAAG;QACA,SAAS,EAAE,MAAM,CAAC;QAClB;;;;WAIG;QACH,IAAI,EAAE,MAAM,CAAC;KAChB,GAAG;QACA,SAAS,EAAE,QAAQ,CAAC;QACpB;;;;WAIG;QACH,MAAM,EAAE,MAAM,CAAC;KAClB,GAAG;QACA,SAAS,EAAE,OAAO,CAAC;QACnB;;;;WAIG;QACH,KAAK,EAAE,MAAM,CAAC;KACjB,GAAG;QACA,SAAS,EAAE,QAAQ,CAAC;QACpB;;;;;;;WAOG;QACH,MAAM,EAAE,iBAAiB,CAAC;KAC7B,GAAG;QACA,SAAS,EAAE,SAAS,CAAC;KACxB,CAAC;IACF;;;;;;;;;OASG;IACH,IAAI,EAAE,MAAM,CAAC;IACb;;;;;;;;;OASG;IACH,YAAY,EAAE,MAAM,CAAC;IACrB;;;;;;OAMG;IACH,kBAAkB,EAAE,QAAQ,EAAE,CAAC;CAClC;AACD;;;;GAIG;AACH,MAAM,WAAW,iBAAiB;IAC9B;;;;OAIG;IACH,IAAI,EAAE,MAAM,CAAC;IACb;;;;OAIG;IACH,IAAI,EAAE,MAAM,CAAC;CAChB;AAED,cAAM,SAAU,SAAQ,WAAW,CAAC,IAAI,CAAC;;IAOrC,MAAM,CAAC,KAAK,CAAC,EAAE,cAAc,CAAC,IAAI,CAAC,GAAG,IAAI;IAO1C,kBAAkB,CAAC,MAAM,EAAE,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,iBAAiB,EAAE,MAAM,CAAC,EAAE,IAAI,GAAG,IAAI;IAsB1G,mBAAmB,CAAC,OAAO,EAAE,IAAI,EAAE,MAAM,EAAE,aAAa,EAAE,OAAO,EAAE,kBAAkB,GAAG,aAAa;CAYxG;AACD;;GAEG;AACH,eAAO,MAAM,IAAI,WAAkB,CAAC;AAEpC,cAAM,aAAc,SAAQ,WAAW,CAAC,QAAQ,CAAC;;IAe7C,MAAM,CAAC,KAAK,CAAC,EAAE,cAAc,CAAC,QAAQ,CAAC,GAAG,QAAQ;IAOlD,kBAAkB,CAAC,MAAM,EAAE,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,iBAAiB,EAAE,MAAM,CAAC,EAAE,QAAQ,GAAG,QAAQ;IAgElH,mBAAmB,CAAC,OAAO,EAAE,QAAQ,EAAE,MAAM,EAAE,aAAa,EAAE,OAAO,EAAE,kBAAkB,GAAG,aAAa;CAoC5G;AACD;;GAEG;AACH,eAAO,MAAM,QAAQ,eAAsB,CAAC;AAE5C,cAAM,sBAAuB,SAAQ,WAAW,CAAC,iBAAiB,CAAC;;IAO/D,MAAM,CAAC,KAAK,CAAC,EAAE,cAAc,CAAC,iBAAiB,CAAC,GAAG,iBAAiB;IAOpE,kBAAkB,CAAC,MAAM,EAAE,aAAa,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,iBAAiB,EAAE,MAAM,CAAC,EAAE,iBAAiB,GAAG,iBAAiB;IAsBpI,mBAAmB,CAAC,OAAO,EAAE,iBAAiB,EAAE,MAAM,EAAE,aAAa,EAAE,OAAO,EAAE,kBAAkB,GAAG,aAAa;CAYrH;AACD;;GAEG;AACH,eAAO,MAAM,iBAAiB,wBAA+B,CAAC"}
@@ -0,0 +1,78 @@
1
+ /**
2
+ * The launch stage as defined by [Google Cloud Platform
3
+ * Launch Stages](https://cloud.google.com/terms/launch-stages).
4
+ *
5
+ * @generated from protobuf enum google.api.LaunchStage
6
+ */
7
+ export declare enum LaunchStage {
8
+ /**
9
+ * Do not use this default value.
10
+ *
11
+ * @generated from protobuf enum value: LAUNCH_STAGE_UNSPECIFIED = 0;
12
+ */
13
+ LAUNCH_STAGE_UNSPECIFIED = 0,
14
+ /**
15
+ * The feature is not yet implemented. Users can not use it.
16
+ *
17
+ * @generated from protobuf enum value: UNIMPLEMENTED = 6;
18
+ */
19
+ UNIMPLEMENTED = 6,
20
+ /**
21
+ * Prelaunch features are hidden from users and are only visible internally.
22
+ *
23
+ * @generated from protobuf enum value: PRELAUNCH = 7;
24
+ */
25
+ PRELAUNCH = 7,
26
+ /**
27
+ * Early Access features are limited to a closed group of testers. To use
28
+ * these features, you must sign up in advance and sign a Trusted Tester
29
+ * agreement (which includes confidentiality provisions). These features may
30
+ * be unstable, changed in backward-incompatible ways, and are not
31
+ * guaranteed to be released.
32
+ *
33
+ * @generated from protobuf enum value: EARLY_ACCESS = 1;
34
+ */
35
+ EARLY_ACCESS = 1,
36
+ /**
37
+ * Alpha is a limited availability test for releases before they are cleared
38
+ * for widespread use. By Alpha, all significant design issues are resolved
39
+ * and we are in the process of verifying functionality. Alpha customers
40
+ * need to apply for access, agree to applicable terms, and have their
41
+ * projects allowlisted. Alpha releases don't have to be feature complete,
42
+ * no SLAs are provided, and there are no technical support obligations, but
43
+ * they will be far enough along that customers can actually use them in
44
+ * test environments or for limited-use tests -- just like they would in
45
+ * normal production cases.
46
+ *
47
+ * @generated from protobuf enum value: ALPHA = 2;
48
+ */
49
+ ALPHA = 2,
50
+ /**
51
+ * Beta is the point at which we are ready to open a release for any
52
+ * customer to use. There are no SLA or technical support obligations in a
53
+ * Beta release. Products will be complete from a feature perspective, but
54
+ * may have some open outstanding issues. Beta releases are suitable for
55
+ * limited production use cases.
56
+ *
57
+ * @generated from protobuf enum value: BETA = 3;
58
+ */
59
+ BETA = 3,
60
+ /**
61
+ * GA features are open to all developers and are considered stable and
62
+ * fully qualified for production use.
63
+ *
64
+ * @generated from protobuf enum value: GA = 4;
65
+ */
66
+ GA = 4,
67
+ /**
68
+ * Deprecated features are scheduled to be shut down and removed. For more
69
+ * information, see the "Deprecation Policy" section of our [Terms of
70
+ * Service](https://cloud.google.com/terms/)
71
+ * and the [Google Cloud Platform Subject to the Deprecation
72
+ * Policy](https://cloud.google.com/terms/deprecation) documentation.
73
+ *
74
+ * @generated from protobuf enum value: DEPRECATED = 5;
75
+ */
76
+ DEPRECATED = 5
77
+ }
78
+ //# sourceMappingURL=launch_stage.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"launch_stage.d.ts","sourceRoot":"","sources":["../../../../src/genproto/google/api/launch_stage.ts"],"names":[],"mappings":"AAkBA;;;;;GAKG;AACH,oBAAY,WAAW;IACnB;;;;OAIG;IACH,wBAAwB,IAAI;IAC5B;;;;OAIG;IACH,aAAa,IAAI;IACjB;;;;OAIG;IACH,SAAS,IAAI;IACb;;;;;;;;OAQG;IACH,YAAY,IAAI;IAChB;;;;;;;;;;;;OAYG;IACH,KAAK,IAAI;IACT;;;;;;;;OAQG;IACH,IAAI,IAAI;IACR;;;;;OAKG;IACH,EAAE,IAAI;IACN;;;;;;;;OAQG;IACH,UAAU,IAAI;CACjB"}