sift-stack-py 0.3.2__py3-none-any.whl

google/api/http_pb2.pyi

@@ -0,0 +1,433 @@
+"""
+@generated by mypy-protobuf.  Do not edit manually!
+isort:skip_file
+Copyright 2024 Google LLC
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+"""
+
+import builtins
+import collections.abc
+import google.protobuf.descriptor
+import google.protobuf.internal.containers
+import google.protobuf.message
+import typing
+
+DESCRIPTOR: google.protobuf.descriptor.FileDescriptor
+
+@typing.final
+class Http(google.protobuf.message.Message):
+    """Defines the HTTP configuration for an API service. It contains a list of
+    [HttpRule][google.api.HttpRule], each specifying the mapping of an RPC method
+    to one or more HTTP REST API methods.
+    """
+
+    DESCRIPTOR: google.protobuf.descriptor.Descriptor
+
+    RULES_FIELD_NUMBER: builtins.int
+    FULLY_DECODE_RESERVED_EXPANSION_FIELD_NUMBER: builtins.int
+    fully_decode_reserved_expansion: builtins.bool
+    """When set to true, URL path parameters will be fully URI-decoded except in
+    cases of single segment matches in reserved expansion, where "%2F" will be
+    left encoded.
+
+    The default behavior is to not decode RFC 6570 reserved characters in multi
+    segment matches.
+    """
+    @property
+    def rules(self) -> google.protobuf.internal.containers.RepeatedCompositeFieldContainer[global___HttpRule]:
+        """A list of HTTP configuration rules that apply to individual API methods.
+
+        **NOTE:** All service configuration rules follow "last one wins" order.
+        """
+
+    def __init__(
+        self,
+        *,
+        rules: collections.abc.Iterable[global___HttpRule] | None = ...,
+        fully_decode_reserved_expansion: builtins.bool = ...,
+    ) -> None: ...
+    def ClearField(self, field_name: typing.Literal["fully_decode_reserved_expansion", b"fully_decode_reserved_expansion", "rules", b"rules"]) -> None: ...
+
+global___Http = Http
+
+@typing.final
+class HttpRule(google.protobuf.message.Message):
+    """gRPC Transcoding
+
+    gRPC Transcoding is a feature for mapping between a gRPC method and one or
+    more HTTP REST endpoints. It allows developers to build a single API service
+    that supports both gRPC APIs and REST APIs. Many systems, including [Google
+    APIs](https://github.com/googleapis/googleapis),
+    [Cloud Endpoints](https://cloud.google.com/endpoints), [gRPC
+    Gateway](https://github.com/grpc-ecosystem/grpc-gateway),
+    and [Envoy](https://github.com/envoyproxy/envoy) proxy support this feature
+    and use it for large scale production services.
+
+    `HttpRule` defines the schema of the gRPC/REST mapping. The mapping specifies
+    how different portions of the gRPC request message are mapped to the URL
+    path, URL query parameters, and HTTP request body. It also controls how the
+    gRPC response message is mapped to the HTTP response body. `HttpRule` is
+    typically specified as an `google.api.http` annotation on the gRPC method.
+
+    Each mapping specifies a URL path template and an HTTP method. The path
+    template may refer to one or more fields in the gRPC request message, as long
+    as each field is a non-repeated field with a primitive (non-message) type.
+    The path template controls how fields of the request message are mapped to
+    the URL path.
+
+    Example:
+
+        service Messaging {
+          rpc GetMessage(GetMessageRequest) returns (Message) {
+            option (google.api.http) = {
+                get: "/v1/{name=messages/*}"
+            };
+          }
+        }
+        message GetMessageRequest {
+          string name = 1; // Mapped to URL path.
+        }
+        message Message {
+          string text = 1; // The resource content.
+        }
+
+    This enables an HTTP REST to gRPC mapping as below:
+
+    - HTTP: `GET /v1/messages/123456`
+    - gRPC: `GetMessage(name: "messages/123456")`
+
+    Any fields in the request message which are not bound by the path template
+    automatically become HTTP query parameters if there is no HTTP request body.
+    For example:
+
+        service Messaging {
+          rpc GetMessage(GetMessageRequest) returns (Message) {
+            option (google.api.http) = {
+                get:"/v1/messages/{message_id}"
+            };
+          }
+        }
+        message GetMessageRequest {
+          message SubMessage {
+            string subfield = 1;
+          }
+          string message_id = 1; // Mapped to URL path.
+          int64 revision = 2;    // Mapped to URL query parameter `revision`.
+          SubMessage sub = 3;    // Mapped to URL query parameter `sub.subfield`.
+        }
+
+    This enables a HTTP JSON to RPC mapping as below:
+
+    - HTTP: `GET /v1/messages/123456?revision=2&sub.subfield=foo`
+    - gRPC: `GetMessage(message_id: "123456" revision: 2 sub:
+    SubMessage(subfield: "foo"))`
+
+    Note that fields which are mapped to URL query parameters must have a
+    primitive type or a repeated primitive type or a non-repeated message type.
+    In the case of a repeated type, the parameter can be repeated in the URL
+    as `...?param=A&param=B`. In the case of a message type, each field of the
+    message is mapped to a separate parameter, such as
+    `...?foo.a=A&foo.b=B&foo.c=C`.
+
+    For HTTP methods that allow a request body, the `body` field
+    specifies the mapping. Consider a REST update method on the
+    message resource collection:
+
+        service Messaging {
+          rpc UpdateMessage(UpdateMessageRequest) returns (Message) {
+            option (google.api.http) = {
+              patch: "/v1/messages/{message_id}"
+              body: "message"
+            };
+          }
+        }
+        message UpdateMessageRequest {
+          string message_id = 1; // mapped to the URL
+          Message message = 2;   // mapped to the body
+        }
+
+    The following HTTP JSON to RPC mapping is enabled, where the
+    representation of the JSON in the request body is determined by
+    protos JSON encoding:
+
+    - HTTP: `PATCH /v1/messages/123456 { "text": "Hi!" }`
+    - gRPC: `UpdateMessage(message_id: "123456" message { text: "Hi!" })`
+
+    The special name `*` can be used in the body mapping to define that
+    every field not bound by the path template should be mapped to the
+    request body.  This enables the following alternative definition of
+    the update method:
+
+        service Messaging {
+          rpc UpdateMessage(Message) returns (Message) {
+            option (google.api.http) = {
+              patch: "/v1/messages/{message_id}"
+              body: "*"
+            };
+          }
+        }
+        message Message {
+          string message_id = 1;
+          string text = 2;
+        }
+
+
+    The following HTTP JSON to RPC mapping is enabled:
+
+    - HTTP: `PATCH /v1/messages/123456 { "text": "Hi!" }`
+    - gRPC: `UpdateMessage(message_id: "123456" text: "Hi!")`
+
+    Note that when using `*` in the body mapping, it is not possible to
+    have HTTP parameters, as all fields not bound by the path end in
+    the body. This makes this option more rarely used in practice when
+    defining REST APIs. The common usage of `*` is in custom methods
+    which don't use the URL at all for transferring data.
+
+    It is possible to define multiple HTTP methods for one RPC by using
+    the `additional_bindings` option. Example:
+
+        service Messaging {
+          rpc GetMessage(GetMessageRequest) returns (Message) {
+            option (google.api.http) = {
+              get: "/v1/messages/{message_id}"
+              additional_bindings {
+                get: "/v1/users/{user_id}/messages/{message_id}"
+              }
+            };
+          }
+        }
+        message GetMessageRequest {
+          string message_id = 1;
+          string user_id = 2;
+        }
+
+    This enables the following two alternative HTTP JSON to RPC mappings:
+
+    - HTTP: `GET /v1/messages/123456`
+    - gRPC: `GetMessage(message_id: "123456")`
+
+    - HTTP: `GET /v1/users/me/messages/123456`
+    - gRPC: `GetMessage(user_id: "me" message_id: "123456")`
+
+    Rules for HTTP mapping
+
+    1. Leaf request fields (recursive expansion nested messages in the request
+       message) are classified into three categories:
+       - Fields referred by the path template. They are passed via the URL path.
+       - Fields referred by the [HttpRule.body][google.api.HttpRule.body]. They
+       are passed via the HTTP
+         request body.
+       - All other fields are passed via the URL query parameters, and the
+         parameter name is the field path in the request message. A repeated
+         field can be represented as multiple query parameters under the same
+         name.
+     2. If [HttpRule.body][google.api.HttpRule.body] is "*", there is no URL
+     query parameter, all fields
+        are passed via URL path and HTTP request body.
+     3. If [HttpRule.body][google.api.HttpRule.body] is omitted, there is no HTTP
+     request body, all
+        fields are passed via URL path and URL query parameters.
+
+    Path template syntax
+
+        Template = "/" Segments [ Verb ] ;
+        Segments = Segment { "/" Segment } ;
+        Segment  = "*" | "**" | LITERAL | Variable ;
+        Variable = "{" FieldPath [ "=" Segments ] "}" ;
+        FieldPath = IDENT { "." IDENT } ;
+        Verb     = ":" LITERAL ;
+
+    The syntax `*` matches a single URL path segment. The syntax `**` matches
+    zero or more URL path segments, which must be the last part of the URL path
+    except the `Verb`.
+
+    The syntax `Variable` matches part of the URL path as specified by its
+    template. A variable template must not contain other variables. If a variable
+    matches a single path segment, its template may be omitted, e.g. `{var}`
+    is equivalent to `{var=*}`.
+
+    The syntax `LITERAL` matches literal text in the URL path. If the `LITERAL`
+    contains any reserved character, such characters should be percent-encoded
+    before the matching.
+
+    If a variable contains exactly one path segment, such as `"{var}"` or
+    `"{var=*}"`, when such a variable is expanded into a URL path on the client
+    side, all characters except `[-_.~0-9a-zA-Z]` are percent-encoded. The
+    server side does the reverse decoding. Such variables show up in the
+    [Discovery
+    Document](https://developers.google.com/discovery/v1/reference/apis) as
+    `{var}`.
+
+    If a variable contains multiple path segments, such as `"{var=foo/*}"`
+    or `"{var=**}"`, when such a variable is expanded into a URL path on the
+    client side, all characters except `[-_.~/0-9a-zA-Z]` are percent-encoded.
+    The server side does the reverse decoding, except "%2F" and "%2f" are left
+    unchanged. Such variables show up in the
+    [Discovery
+    Document](https://developers.google.com/discovery/v1/reference/apis) as
+    `{+var}`.
+
+    Using gRPC API Service Configuration
+
+    gRPC API Service Configuration (service config) is a configuration language
+    for configuring a gRPC service to become a user-facing product. The
+    service config is simply the YAML representation of the `google.api.Service`
+    proto message.
+
+    As an alternative to annotating your proto file, you can configure gRPC
+    transcoding in your service config YAML files. You do this by specifying a
+    `HttpRule` that maps the gRPC method to a REST endpoint, achieving the same
+    effect as the proto annotation. This can be particularly useful if you
+    have a proto that is reused in multiple services. Note that any transcoding
+    specified in the service config will override any matching transcoding
+    configuration in the proto.
+
+    The following example selects a gRPC method and applies an `HttpRule` to it:
+
+        http:
+          rules:
+            - selector: example.v1.Messaging.GetMessage
+              get: /v1/messages/{message_id}/{sub.subfield}
+
+    Special notes
+
+    When gRPC Transcoding is used to map a gRPC to JSON REST endpoints, the
+    proto to JSON conversion must follow the [proto3
+    specification](https://developers.google.com/protocol-buffers/docs/proto3#json).
+
+    While the single segment variable follows the semantics of
+    [RFC 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2 Simple String
+    Expansion, the multi segment variable **does not** follow RFC 6570 Section
+    3.2.3 Reserved Expansion. The reason is that the Reserved Expansion
+    does not expand special characters like `?` and `#`, which would lead
+    to invalid URLs. As the result, gRPC Transcoding uses a custom encoding
+    for multi segment variables.
+
+    The path variables **must not** refer to any repeated or mapped field,
+    because client libraries are not capable of handling such variable expansion.
+
+    The path variables **must not** capture the leading "/" character. The reason
+    is that the most common use case "{var}" does not capture the leading "/"
+    character. For consistency, all path variables must share the same behavior.
+
+    Repeated message fields must not be mapped to URL query parameters, because
+    no client library can support such complicated mapping.
+
+    If an API needs to use a JSON array for request or response body, it can map
+    the request or response body to a repeated field. However, some gRPC
+    Transcoding implementations may not support this feature.
+    """
+
+    DESCRIPTOR: google.protobuf.descriptor.Descriptor
+
+    SELECTOR_FIELD_NUMBER: builtins.int
+    GET_FIELD_NUMBER: builtins.int
+    PUT_FIELD_NUMBER: builtins.int
+    POST_FIELD_NUMBER: builtins.int
+    DELETE_FIELD_NUMBER: builtins.int
+    PATCH_FIELD_NUMBER: builtins.int
+    CUSTOM_FIELD_NUMBER: builtins.int
+    BODY_FIELD_NUMBER: builtins.int
+    RESPONSE_BODY_FIELD_NUMBER: builtins.int
+    ADDITIONAL_BINDINGS_FIELD_NUMBER: builtins.int
+    selector: builtins.str
+    """Selects a method to which this rule applies.
+
+    Refer to [selector][google.api.DocumentationRule.selector] for syntax
+    details.
+    """
+    get: builtins.str
+    """Maps to HTTP GET. Used for listing and getting information about
+    resources.
+    """
+    put: builtins.str
+    """Maps to HTTP PUT. Used for replacing a resource."""
+    post: builtins.str
+    """Maps to HTTP POST. Used for creating a resource or performing an action."""
+    delete: builtins.str
+    """Maps to HTTP DELETE. Used for deleting a resource."""
+    patch: builtins.str
+    """Maps to HTTP PATCH. Used for updating a resource."""
+    body: builtins.str
+    """The name of the request field whose value is mapped to the HTTP request
+    body, or `*` for mapping all request fields not captured by the path
+    pattern to the HTTP body, or omitted for not having any HTTP request body.
+
+    NOTE: the referred field must be present at the top-level of the request
+    message type.
+    """
+    response_body: builtins.str
+    """Optional. The name of the response field whose value is mapped to the HTTP
+    response body. When omitted, the entire response message will be used
+    as the HTTP response body.
+
+    NOTE: The referred field must be present at the top-level of the response
+    message type.
+    """
+    @property
+    def custom(self) -> global___CustomHttpPattern:
+        """The custom pattern is used for specifying an HTTP method that is not
+        included in the `pattern` field, such as HEAD, or "*" to leave the
+        HTTP method unspecified for this rule. The wild-card rule is useful
+        for services that provide content to Web (HTML) clients.
+        """
+
+    @property
+    def additional_bindings(self) -> google.protobuf.internal.containers.RepeatedCompositeFieldContainer[global___HttpRule]:
+        """Additional HTTP bindings for the selector. Nested bindings must
+        not contain an `additional_bindings` field themselves (that is,
+        the nesting may only be one level deep).
+        """
+
+    def __init__(
+        self,
+        *,
+        selector: builtins.str = ...,
+        get: builtins.str = ...,
+        put: builtins.str = ...,
+        post: builtins.str = ...,
+        delete: builtins.str = ...,
+        patch: builtins.str = ...,
+        custom: global___CustomHttpPattern | None = ...,
+        body: builtins.str = ...,
+        response_body: builtins.str = ...,
+        additional_bindings: collections.abc.Iterable[global___HttpRule] | None = ...,
+    ) -> None: ...
+    def HasField(self, field_name: typing.Literal["custom", b"custom", "delete", b"delete", "get", b"get", "patch", b"patch", "pattern", b"pattern", "post", b"post", "put", b"put"]) -> builtins.bool: ...
+    def ClearField(self, field_name: typing.Literal["additional_bindings", b"additional_bindings", "body", b"body", "custom", b"custom", "delete", b"delete", "get", b"get", "patch", b"patch", "pattern", b"pattern", "post", b"post", "put", b"put", "response_body", b"response_body", "selector", b"selector"]) -> None: ...
+    def WhichOneof(self, oneof_group: typing.Literal["pattern", b"pattern"]) -> typing.Literal["get", "put", "post", "delete", "patch", "custom"] | None: ...
+
+global___HttpRule = HttpRule
+
+@typing.final
+class CustomHttpPattern(google.protobuf.message.Message):
+    """A custom pattern is used for defining custom HTTP verb."""
+
+    DESCRIPTOR: google.protobuf.descriptor.Descriptor
+
+    KIND_FIELD_NUMBER: builtins.int
+    PATH_FIELD_NUMBER: builtins.int
+    kind: builtins.str
+    """The name of this custom HTTP verb."""
+    path: builtins.str
+    """The path matched by this custom verb."""
+    def __init__(
+        self,
+        *,
+        kind: builtins.str = ...,
+        path: builtins.str = ...,
+    ) -> None: ...
+    def ClearField(self, field_name: typing.Literal["kind", b"kind", "path", b"path"]) -> None: ...
+
+global___CustomHttpPattern = CustomHttpPattern

google/api/http_pb2_grpc.py

@@ -0,0 +1,4 @@
+# Generated by the gRPC Python protocol compiler plugin. DO NOT EDIT!
+"""Client and server classes corresponding to protobuf-defined services."""
+import grpc
+

google/api/http_pb2_grpc.pyi

@@ -0,0 +1,30 @@
+"""
+@generated by mypy-protobuf.  Do not edit manually!
+isort:skip_file
+Copyright 2024 Google LLC
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+"""
+
+import abc
+import collections.abc
+import grpc
+import grpc.aio
+import typing
+
+_T = typing.TypeVar("_T")
+
+class _MaybeAsyncIterator(collections.abc.AsyncIterator[_T], collections.abc.Iterator[_T], metaclass=abc.ABCMeta): ...
+
+class _ServicerContext(grpc.ServicerContext, grpc.aio.ServicerContext):  # type: ignore[misc, type-arg]
+    ...

protoc_gen_openapiv2/options/annotations_pb2.py

@@ -0,0 +1,27 @@
+# -*- coding: utf-8 -*-
+# Generated by the protocol buffer compiler.  DO NOT EDIT!
+# source: protoc-gen-openapiv2/options/annotations.proto
+# Protobuf Python Version: 5.26.1
+"""Generated protocol buffer code."""
+from google.protobuf import descriptor as _descriptor
+from google.protobuf import descriptor_pool as _descriptor_pool
+from google.protobuf import symbol_database as _symbol_database
+from google.protobuf.internal import builder as _builder
+# @@protoc_insertion_point(imports)
+
+_sym_db = _symbol_database.Default()
+
+
+from google.protobuf import descriptor_pb2 as google_dot_protobuf_dot_descriptor__pb2
+from protoc_gen_openapiv2.options import openapiv2_pb2 as protoc__gen__openapiv2_dot_options_dot_openapiv2__pb2
+
+
+DESCRIPTOR = _descriptor_pool.Default().AddSerializedFile(b'\n.protoc-gen-openapiv2/options/annotations.proto\x12)grpc.gateway.protoc_gen_openapiv2.options\x1a google/protobuf/descriptor.proto\x1a,protoc-gen-openapiv2/options/openapiv2.proto:~\n\x11openapiv2_swagger\x12\x1c.google.protobuf.FileOptions\x18\x92\x08 \x01(\x0b\x32\x32.grpc.gateway.protoc_gen_openapiv2.options.SwaggerR\x10openapiv2Swagger:\x86\x01\n\x13openapiv2_operation\x12\x1e.google.protobuf.MethodOptions\x18\x92\x08 \x01(\x0b\x32\x34.grpc.gateway.protoc_gen_openapiv2.options.OperationR\x12openapiv2Operation:~\n\x10openapiv2_schema\x12\x1f.google.protobuf.MessageOptions\x18\x92\x08 \x01(\x0b\x32\x31.grpc.gateway.protoc_gen_openapiv2.options.SchemaR\x0fopenapiv2Schema:u\n\ropenapiv2_tag\x12\x1f.google.protobuf.ServiceOptions\x18\x92\x08 \x01(\x0b\x32..grpc.gateway.protoc_gen_openapiv2.options.TagR\x0copenapiv2Tag:~\n\x0fopenapiv2_field\x12\x1d.google.protobuf.FieldOptions\x18\x92\x08 \x01(\x0b\x32\x35.grpc.gateway.protoc_gen_openapiv2.options.JSONSchemaR\x0eopenapiv2FieldB\xc9\x02\n-com.grpc.gateway.protoc_gen_openapiv2.optionsB\x10\x41nnotationsProtoP\x01ZFgithub.com/grpc-ecosystem/grpc-gateway/v2/protoc-gen-openapiv2/options\xa2\x02\x04GGPO\xaa\x02\'Grpc.Gateway.ProtocGenOpenapiv2.Options\xca\x02\'Grpc\\Gateway\\ProtocGenOpenapiv2\\Options\xe2\x02\x33Grpc\\Gateway\\ProtocGenOpenapiv2\\Options\\GPBMetadata\xea\x02*Grpc::Gateway::ProtocGenOpenapiv2::Optionsb\x06proto3')
+
+_globals = globals()
+_builder.BuildMessageAndEnumDescriptors(DESCRIPTOR, _globals)
+_builder.BuildTopDescriptorsAndMessages(DESCRIPTOR, 'protoc_gen_openapiv2.options.annotations_pb2', _globals)
+if not _descriptor._USE_C_DESCRIPTORS:
+  _globals['DESCRIPTOR']._loaded_options = None
+  _globals['DESCRIPTOR']._serialized_options = b'\n-com.grpc.gateway.protoc_gen_openapiv2.optionsB\020AnnotationsProtoP\001ZFgithub.com/grpc-ecosystem/grpc-gateway/v2/protoc-gen-openapiv2/options\242\002\004GGPO\252\002\'Grpc.Gateway.ProtocGenOpenapiv2.Options\312\002\'Grpc\\Gateway\\ProtocGenOpenapiv2\\Options\342\0023Grpc\\Gateway\\ProtocGenOpenapiv2\\Options\\GPBMetadata\352\002*Grpc::Gateway::ProtocGenOpenapiv2::Options'
+# @@protoc_insertion_point(module_scope)

protoc_gen_openapiv2/options/annotations_pb2.pyi

@@ -0,0 +1,48 @@
+"""
+@generated by mypy-protobuf.  Do not edit manually!
+isort:skip_file
+"""
+
+import builtins
+import google.protobuf.descriptor
+import google.protobuf.descriptor_pb2
+import google.protobuf.internal.extension_dict
+import protoc_gen_openapiv2.options.openapiv2_pb2
+
+DESCRIPTOR: google.protobuf.descriptor.FileDescriptor
+
+OPENAPIV2_SWAGGER_FIELD_NUMBER: builtins.int
+OPENAPIV2_OPERATION_FIELD_NUMBER: builtins.int
+OPENAPIV2_SCHEMA_FIELD_NUMBER: builtins.int
+OPENAPIV2_TAG_FIELD_NUMBER: builtins.int
+OPENAPIV2_FIELD_FIELD_NUMBER: builtins.int
+openapiv2_swagger: google.protobuf.internal.extension_dict._ExtensionFieldDescriptor[google.protobuf.descriptor_pb2.FileOptions, protoc_gen_openapiv2.options.openapiv2_pb2.Swagger]
+"""ID assigned by protobuf-global-extension-registry@google.com for gRPC-Gateway project.
+
+All IDs are the same, as assigned. It is okay that they are the same, as they extend
+different descriptor messages.
+"""
+openapiv2_operation: google.protobuf.internal.extension_dict._ExtensionFieldDescriptor[google.protobuf.descriptor_pb2.MethodOptions, protoc_gen_openapiv2.options.openapiv2_pb2.Operation]
+"""ID assigned by protobuf-global-extension-registry@google.com for gRPC-Gateway project.
+
+All IDs are the same, as assigned. It is okay that they are the same, as they extend
+different descriptor messages.
+"""
+openapiv2_schema: google.protobuf.internal.extension_dict._ExtensionFieldDescriptor[google.protobuf.descriptor_pb2.MessageOptions, protoc_gen_openapiv2.options.openapiv2_pb2.Schema]
+"""ID assigned by protobuf-global-extension-registry@google.com for gRPC-Gateway project.
+
+All IDs are the same, as assigned. It is okay that they are the same, as they extend
+different descriptor messages.
+"""
+openapiv2_tag: google.protobuf.internal.extension_dict._ExtensionFieldDescriptor[google.protobuf.descriptor_pb2.ServiceOptions, protoc_gen_openapiv2.options.openapiv2_pb2.Tag]
+"""ID assigned by protobuf-global-extension-registry@google.com for gRPC-Gateway project.
+
+All IDs are the same, as assigned. It is okay that they are the same, as they extend
+different descriptor messages.
+"""
+openapiv2_field: google.protobuf.internal.extension_dict._ExtensionFieldDescriptor[google.protobuf.descriptor_pb2.FieldOptions, protoc_gen_openapiv2.options.openapiv2_pb2.JSONSchema]
+"""ID assigned by protobuf-global-extension-registry@google.com for gRPC-Gateway project.
+
+All IDs are the same, as assigned. It is okay that they are the same, as they extend
+different descriptor messages.
+"""

protoc_gen_openapiv2/options/annotations_pb2_grpc.py

@@ -0,0 +1,4 @@
+# Generated by the gRPC Python protocol compiler plugin. DO NOT EDIT!
+"""Client and server classes corresponding to protobuf-defined services."""
+import grpc
+

protoc_gen_openapiv2/options/annotations_pb2_grpc.pyi

@@ -0,0 +1,17 @@
+"""
+@generated by mypy-protobuf.  Do not edit manually!
+isort:skip_file
+"""
+
+import abc
+import collections.abc
+import grpc
+import grpc.aio
+import typing
+
+_T = typing.TypeVar("_T")
+
+class _MaybeAsyncIterator(collections.abc.AsyncIterator[_T], collections.abc.Iterator[_T], metaclass=abc.ABCMeta): ...
+
+class _ServicerContext(grpc.ServicerContext, grpc.aio.ServicerContext):  # type: ignore[misc, type-arg]
+    ...