Interface DynamicModuleFilterPerRouteOrBuilder
- All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder,com.google.protobuf.MessageOrBuilder
- All Known Implementing Classes:
DynamicModuleFilterPerRoute,DynamicModuleFilterPerRoute.Builder
public interface DynamicModuleFilterPerRouteOrBuilder
extends com.google.protobuf.MessageOrBuilder
-
Method Summary
Modifier and TypeMethodDescriptionSpecifies the shared-object level configuration.Specifies the shared-object level configuration.com.google.protobuf.AnyThe configuration for the filter chosen by ``per_route_config_name``.com.google.protobuf.AnyOrBuilderThe configuration for the filter chosen by ``per_route_config_name``.The name for this filter configuration.com.google.protobuf.ByteStringThe name for this filter configuration.booleanSpecifies the shared-object level configuration.booleanThe configuration for the filter chosen by ``per_route_config_name``.Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder
isInitializedMethods inherited from interface com.google.protobuf.MessageOrBuilder
findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
-
Method Details
-
hasDynamicModuleConfig
boolean hasDynamicModuleConfig()Specifies the shared-object level configuration.
.envoy.extensions.dynamic_modules.v3.DynamicModuleConfig dynamic_module_config = 1;- Returns:
- Whether the dynamicModuleConfig field is set.
-
getDynamicModuleConfig
DynamicModuleConfig getDynamicModuleConfig()Specifies the shared-object level configuration.
.envoy.extensions.dynamic_modules.v3.DynamicModuleConfig dynamic_module_config = 1;- Returns:
- The dynamicModuleConfig.
-
getDynamicModuleConfigOrBuilder
DynamicModuleConfigOrBuilder getDynamicModuleConfigOrBuilder()Specifies the shared-object level configuration.
.envoy.extensions.dynamic_modules.v3.DynamicModuleConfig dynamic_module_config = 1; -
getPerRouteConfigName
String getPerRouteConfigName()The name for this filter configuration. This can be used to distinguish between different filter implementations inside a dynamic module. For example, a module can have completely different filter implementations. When Envoy receives this configuration, it passes the ``per_route_config_name`` to the dynamic module's HTTP per-route filter config init function together with the ``filter_config``. That way a module can decide which in-module filter implementation to use based on the name at load time.
string per_route_config_name = 2;- Returns:
- The perRouteConfigName.
-
getPerRouteConfigNameBytes
com.google.protobuf.ByteString getPerRouteConfigNameBytes()The name for this filter configuration. This can be used to distinguish between different filter implementations inside a dynamic module. For example, a module can have completely different filter implementations. When Envoy receives this configuration, it passes the ``per_route_config_name`` to the dynamic module's HTTP per-route filter config init function together with the ``filter_config``. That way a module can decide which in-module filter implementation to use based on the name at load time.
string per_route_config_name = 2;- Returns:
- The bytes for perRouteConfigName.
-
hasFilterConfig
boolean hasFilterConfig()The configuration for the filter chosen by ``per_route_config_name``. This is passed to the module's HTTP per-route filter initialization function. Together with the ``per_route_config_name``, the module can decide which in-module filter implementation to use and fine-tune the behavior of the filter on a specific route. For example, if a module has two filter implementations, one for logging and one for header manipulation, ``per_route_config_name`` is used to choose either logging or header manipulation. The ``filter_config`` can be used to configure the logging level or the header manipulation behavior. ``google.protobuf.Struct`` is serialized as JSON before passing it to the plugin. ``google.protobuf.BytesValue`` and ``google.protobuf.StringValue`` are passed directly without the wrapper. .. code-block:: yaml # Passing in a string filter_config: "@type": "type.googleapis.com/google.protobuf.StringValue" value: hello # Passing in raw bytes filter_config: "@type": "type.googleapis.com/google.protobuf.BytesValue" value: aGVsbG8= # echo -n "hello" | base64.google.protobuf.Any filter_config = 3;- Returns:
- Whether the filterConfig field is set.
-
getFilterConfig
com.google.protobuf.Any getFilterConfig()The configuration for the filter chosen by ``per_route_config_name``. This is passed to the module's HTTP per-route filter initialization function. Together with the ``per_route_config_name``, the module can decide which in-module filter implementation to use and fine-tune the behavior of the filter on a specific route. For example, if a module has two filter implementations, one for logging and one for header manipulation, ``per_route_config_name`` is used to choose either logging or header manipulation. The ``filter_config`` can be used to configure the logging level or the header manipulation behavior. ``google.protobuf.Struct`` is serialized as JSON before passing it to the plugin. ``google.protobuf.BytesValue`` and ``google.protobuf.StringValue`` are passed directly without the wrapper. .. code-block:: yaml # Passing in a string filter_config: "@type": "type.googleapis.com/google.protobuf.StringValue" value: hello # Passing in raw bytes filter_config: "@type": "type.googleapis.com/google.protobuf.BytesValue" value: aGVsbG8= # echo -n "hello" | base64.google.protobuf.Any filter_config = 3;- Returns:
- The filterConfig.
-
getFilterConfigOrBuilder
com.google.protobuf.AnyOrBuilder getFilterConfigOrBuilder()The configuration for the filter chosen by ``per_route_config_name``. This is passed to the module's HTTP per-route filter initialization function. Together with the ``per_route_config_name``, the module can decide which in-module filter implementation to use and fine-tune the behavior of the filter on a specific route. For example, if a module has two filter implementations, one for logging and one for header manipulation, ``per_route_config_name`` is used to choose either logging or header manipulation. The ``filter_config`` can be used to configure the logging level or the header manipulation behavior. ``google.protobuf.Struct`` is serialized as JSON before passing it to the plugin. ``google.protobuf.BytesValue`` and ``google.protobuf.StringValue`` are passed directly without the wrapper. .. code-block:: yaml # Passing in a string filter_config: "@type": "type.googleapis.com/google.protobuf.StringValue" value: hello # Passing in raw bytes filter_config: "@type": "type.googleapis.com/google.protobuf.BytesValue" value: aGVsbG8= # echo -n "hello" | base64.google.protobuf.Any filter_config = 3;
-