The above specifies that all methods in the API request
google.rpc.context.ProjectContext and
google.rpc.context.OriginContext.
Available context types are defined in package
google.rpc.context.
This also provides mechanism to allowlist any protobuf message extension that
can be sent in grpc metadata using “x-goog-ext-<extension_id>-bin” and
“x-goog-ext-<extension_id>-jspb” format. For example, list any service
specific protobuf types that can appear in grpc metadata as follows in your
yaml file:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-12 UTC."],[[["`Context` class defines the contexts that an API can request, using rules to specify which contexts apply to different methods."],["Context rules can specify required context types such as `google.rpc.context.ProjectContext` and `google.rpc.context.OriginContext` for various methods."],["The `Context` class allows for allowlisting protobuf message extensions to be sent in gRPC metadata via specific formats like \"x-goog-ext-\\\u003cextension_id\\\u003e-bin\"."],["The latest version of `Context` is 2.15.0, with older versions 2.10.0 and 2.2.0 also available."],["`Context` class inherits from object and implements interfaces like IMessage, IEquatable, IDeepCloneable, and IBufferMessage, providing methods for cloning, equality checking, and data manipulation."]]],[]]