Get desktop application:
View/edit binary Protocol Buffers messages
At least one of request_rules and response_rules must be provided. Rules to match json body of requests.
Rules to match json body of responses.
[#next-free-field: 6]
Used in:
The namespace — if this is empty, the filter's namespace will be used.
The key to use within the namespace.
The value to pair with the given key. When used for on_present case, if value is non-empty it'll be used instead of the the value of the JSON key. If both are empty, the the value of the JSON key is used as-is. When used for on_missing/on_error case, a non-empty value must be provided. It ignores ValueType, i.e., not type casting.
The value's type — defaults to protobuf.Value.
False if we want to overwrite the existing metadata value. Default to false.
Used in:
The list of rules to apply.
Allowed content-type for json to metadata transformation. Default to ``{"application/json"}``. Set ``allow_empty_content_type`` if empty/missing content-type header is allowed.
Allowed empty content-type for json to metadata transformation. Default to false.
Allowed content-type by regex match for json to metadata transformation. This can be used in parallel with ``allow_content_types``.
A Rule defines what metadata to apply when a key-value is present, missing in the json or fail to parse the payload.
Used in:
Specifies that a match will be performed on the value of a property. Here's an example to match on 1 in {"foo": {"bar": 1}, "bar": 2} selectors: - key: foo - key: bar
If the attribute is present, apply this metadata KeyValuePair.
If the attribute is missing, apply this metadata KeyValuePair. The value in the KeyValuePair must be set.
If the body is too large or fail to parse or content-type is mismatched, apply this metadata KeyValuePair. The value in the KeyValuePair must be set.
Used in:
key to match
Used in:
The value is a serialized `protobuf.Value <https://github.com/protocolbuffers/protobuf/blob/master/src/google/protobuf/struct.proto#L62>`_.