Struct gateway_api::experimental::grpcroutes::GRPCRouteRulesFilters

pub struct GRPCRouteRulesFilters {
    pub extension_ref: Option<GRPCRouteRulesFiltersExtensionRef>,
    pub request_header_modifier: Option<GRPCRouteRulesFiltersRequestHeaderModifier>,
    pub request_mirror: Option<GRPCRouteRulesFiltersRequestMirror>,
    pub type: GRPCRouteRulesFiltersType,
}

GRPCRouteFilter defines processing steps that must be completed during the request or response lifecycle. GRPCRouteFilters are meant as an extension point to express processing that may be done in Gateway implementations. Some examples include request or response modification, implementing authentication strategies, rate-limiting, and traffic shaping. API guarantee/conformance is defined based on the type of the filter.

Fields

extension_ref: Option<GRPCRouteRulesFiltersExtensionRef>

ExtensionRef is an optional, implementation-specific extension to the “filter” behavior. For example, resource “myroutefilter” in group “networking.example.net”). ExtensionRef MUST NOT be used for core and extended filters. Support: Implementation-specific

request_header_modifier: Option<GRPCRouteRulesFiltersRequestHeaderModifier>

RequestHeaderModifier defines a schema for a filter that modifies request headers. Support: Core

request_mirror: Option<GRPCRouteRulesFiltersRequestMirror>

RequestMirror defines a schema for a filter that mirrors requests. Requests are sent to the specified destination, but responses from that destination are ignored. Support: Extended

type: GRPCRouteRulesFiltersType

Type identifies the type of filter to apply. As with other API fields, types are classified into three conformance levels:

• Core: Filter types and their corresponding configuration defined by “Support: Core” in this package, e.g. “RequestHeaderModifier”. All implementations supporting GRPCRoute MUST support core filters.
• Extended: Filter types and their corresponding configuration defined by “Support: Extended” in this package, e.g. “RequestMirror”. Implementers are encouraged to support extended filters.
• Implementation-specific: Filters that are defined and supported by specific vendors. In the future, filters showing convergence in behavior across multiple implementations will be considered for inclusion in extended or core conformance levels. Filter-specific configuration for such filters is specified using the ExtensionRef field. Type MUST be set to “ExtensionRef” for custom filters. Implementers are encouraged to define custom implementation types to extend the core API with implementation-specific behavior. If a reference to a custom filter type cannot be resolved, the filter MUST NOT be skipped. Instead, requests that would have been processed by that filter MUST receive a HTTP error response.

Trait Implementations

impl Clone for GRPCRouteRulesFilters

fn clone(&self) -> GRPCRouteRulesFilters

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for GRPCRouteRulesFilters

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for GRPCRouteRulesFilters

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
    __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl JsonSchema for GRPCRouteRulesFilters

fn schema_name() -> String

The name of the generated JSON Schema.

fn json_schema(gen: &mut SchemaGenerator) -> Schema

Generates a JSON Schema for this type.

fn is_referenceable() -> bool

Whether JSON Schemas generated for this type should be re-used where possible using the $ref keyword.

impl Serialize for GRPCRouteRulesFilters

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>where
    __S: Serializer,

Serialize this value into the given Serde serializer.