Get desktop application:
View/edit binary Protocol Buffers messages
Either parsed or checked representation of the `Common Expression Language <https://github.com/google/cel-spec>`_ (CEL) program.
Used in:
, ,Parsed expression in abstract syntax tree (AST) form. Deprecated -- use ``cel_expr_parsed`` field instead. If ``cel_expr_parsed`` or ``cel_expr_checked`` is set, this field is not used.
Parsed expression in abstract syntax tree (AST) form that has been successfully type checked. Deprecated -- use ``cel_expr_checked`` field instead. If ``cel_expr_parsed`` or ``cel_expr_checked`` is set, this field is not used.
Parsed expression in abstract syntax tree (AST) form. If ``cel_expr_checked`` is set, this field is not used.
Parsed expression in abstract syntax tree (AST) form that has been successfully type checked. If set, takes precedence over ``cel_expr_parsed``.
Extracts a string by evaluating a `Common Expression Language <https://github.com/google/cel-spec>`_ (CEL) expression against the standardized set of :ref:`HTTP attributes <arch_overview_attributes>`. .. attention:: Besides CEL evaluation raising an error explicitly, CEL program returning a type other than the ``string``, or not returning anything, are considered an error as well. [#comment:TODO(sergiitk): When implemented, add the extension tag.]
The CEL expression used to extract a string from the CEL environment. the "subject string") that should be replaced.
If CEL expression evaluates to an error, this value is be returned to the caller. If not set, the error is propagated to the caller.
Specifies the double start and end of the range using half-open interval semantics [start, end).
Used in:
start of the range (inclusive)
end of the range (exclusive)
Specifies the int32 start and end of the range using half-open interval semantics [start, end).
Used in:
start of the range (inclusive)
end of the range (exclusive)
Specifies the int64 start and end of the range using half-open interval semantics [start, end).
Used in:
start of the range (inclusive)
end of the range (exclusive)
A TypedStruct contains an arbitrary JSON serialized protocol buffer message with a URL that describes the type of the serialized message. This is very similar to google.protobuf.Any, instead of having protocol buffer binary, this employs google.protobuf.Struct as value. This message is intended to be embedded inside Any, so it shouldn't be directly referred from other UDPA messages. When packing an opaque extension config, packing the expected type into Any is preferred wherever possible for its efficiency. TypedStruct should be used only if a proto descriptor is not available, for example if: - A control plane sends opaque message that is originally from external source in human readable format such as JSON or YAML. - The control plane doesn't have the knowledge of the protocol buffer schema hence it cannot serialize the message in protocol buffer binary format. - The DPLB doesn't have have the knowledge of the protocol buffer schema its plugin or extension uses. This has to be indicated in the DPLB capability negotiation. When a DPLB receives a TypedStruct in Any, it should: - Check if the type_url of the TypedStruct matches the type the extension expects. - Convert value to the type described in type_url and perform validation. TODO(lizan): Figure out how TypeStruct should be used with DPLB extensions that doesn't link protobuf descriptor with DPLB itself, (e.g. gRPC LB Plugin, Envoy WASM extensions).
A URL that uniquely identifies the type of the serialize protocol buffer message. This has same semantics and format described in google.protobuf.Any: https://github.com/protocolbuffers/protobuf/blob/master/src/google/protobuf/any.proto
A JSON representation of the above specified type.