Package io.envoyproxy.envoy.extensions.filters.network.redis_proxy.v3

Class RedisProxy.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>
io.envoyproxy.envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, RedisProxyOrBuilder, Cloneable
Enclosing class:
RedisProxy
public static final class RedisProxy.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder> implements RedisProxyOrBuilder
 [#next-free-field: 12]
Protobuf type envoy.extensions.filters.network.redis_proxy.v3.RedisProxy

  • Method Details

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>

    • clear

      public RedisProxy.Builder clear()
      Specified by:
      clear in interface com.google.protobuf.Message.Builder
      Specified by:
      clear in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clear in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.Message.Builder
      Specified by:
      getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
      Overrides:
      getDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>

    • getDefaultInstanceForType

      public RedisProxy getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

      public RedisProxy build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder

    • buildPartial

      public RedisProxy buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder

    • clone

      public RedisProxy.Builder clone()
      Specified by:
      clone in interface com.google.protobuf.Message.Builder
      Specified by:
      clone in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clone in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>

    • setField

      public RedisProxy.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      setField in interface com.google.protobuf.Message.Builder
      Overrides:
      setField in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>

    • clearField

      public RedisProxy.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
      Specified by:
      clearField in interface com.google.protobuf.Message.Builder
      Overrides:
      clearField in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>

    • clearOneof

      public RedisProxy.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
      Specified by:
      clearOneof in interface com.google.protobuf.Message.Builder
      Overrides:
      clearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>

    • setRepeatedField

      public RedisProxy.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
      Specified by:
      setRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      setRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>

    • addRepeatedField

      public RedisProxy.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      addRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      addRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>

    • mergeFrom

      public RedisProxy.Builder mergeFrom(com.google.protobuf.Message other)
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<RedisProxy.Builder>

    • mergeFrom

      public RedisProxy.Builder mergeFrom(RedisProxy other)

    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>

    • mergeFrom

      public RedisProxy.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Specified by:
      mergeFrom in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<RedisProxy.Builder>
      Throws:
      IOException

    • getStatPrefix

      public String getStatPrefix()
       The prefix to use when emitting :ref:`statistics <config_network_filters_redis_proxy_stats>`.
      string stat_prefix = 1 [(.validate.rules) = { ... }
      Specified by:
      getStatPrefix in interface RedisProxyOrBuilder
      Returns:
      The statPrefix.

    • getStatPrefixBytes

      public com.google.protobuf.ByteString getStatPrefixBytes()
       The prefix to use when emitting :ref:`statistics <config_network_filters_redis_proxy_stats>`.
      string stat_prefix = 1 [(.validate.rules) = { ... }
      Specified by:
      getStatPrefixBytes in interface RedisProxyOrBuilder
      Returns:
      The bytes for statPrefix.

    • setStatPrefix

      public RedisProxy.Builder setStatPrefix(String value)
       The prefix to use when emitting :ref:`statistics <config_network_filters_redis_proxy_stats>`.
      string stat_prefix = 1 [(.validate.rules) = { ... }
      Parameters:
      value - The statPrefix to set.
      Returns:
      This builder for chaining.

    • clearStatPrefix

      public RedisProxy.Builder clearStatPrefix()
       The prefix to use when emitting :ref:`statistics <config_network_filters_redis_proxy_stats>`.
      string stat_prefix = 1 [(.validate.rules) = { ... }
      Returns:
      This builder for chaining.

    • setStatPrefixBytes

      public RedisProxy.Builder setStatPrefixBytes(com.google.protobuf.ByteString value)
       The prefix to use when emitting :ref:`statistics <config_network_filters_redis_proxy_stats>`.
      string stat_prefix = 1 [(.validate.rules) = { ... }
      Parameters:
      value - The bytes for statPrefix to set.
      Returns:
      This builder for chaining.

    • hasSettings

      public boolean hasSettings()
       Network settings for the connection pool to the upstream clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.ConnPoolSettings settings = 3 [(.validate.rules) = { ... }
      Specified by:
      hasSettings in interface RedisProxyOrBuilder
      Returns:
      Whether the settings field is set.

    • getSettings

      public RedisProxy.ConnPoolSettings getSettings()
       Network settings for the connection pool to the upstream clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.ConnPoolSettings settings = 3 [(.validate.rules) = { ... }
      Specified by:
      getSettings in interface RedisProxyOrBuilder
      Returns:
      The settings.

    • setSettings

      public RedisProxy.Builder setSettings(RedisProxy.ConnPoolSettings value)
       Network settings for the connection pool to the upstream clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.ConnPoolSettings settings = 3 [(.validate.rules) = { ... }

    • setSettings

      public RedisProxy.Builder setSettings(RedisProxy.ConnPoolSettings.Builder builderForValue)
       Network settings for the connection pool to the upstream clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.ConnPoolSettings settings = 3 [(.validate.rules) = { ... }

    • mergeSettings

      public RedisProxy.Builder mergeSettings(RedisProxy.ConnPoolSettings value)
       Network settings for the connection pool to the upstream clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.ConnPoolSettings settings = 3 [(.validate.rules) = { ... }

    • clearSettings

      public RedisProxy.Builder clearSettings()
       Network settings for the connection pool to the upstream clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.ConnPoolSettings settings = 3 [(.validate.rules) = { ... }

    • getSettingsBuilder

      public RedisProxy.ConnPoolSettings.Builder getSettingsBuilder()
       Network settings for the connection pool to the upstream clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.ConnPoolSettings settings = 3 [(.validate.rules) = { ... }

    • getSettingsOrBuilder

      public RedisProxy.ConnPoolSettingsOrBuilder getSettingsOrBuilder()
       Network settings for the connection pool to the upstream clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.ConnPoolSettings settings = 3 [(.validate.rules) = { ... }
      Specified by:
      getSettingsOrBuilder in interface RedisProxyOrBuilder

    • getLatencyInMicros

      public boolean getLatencyInMicros()
       Indicates that latency stat should be computed in microseconds. By default it is computed in
 milliseconds. This does not apply to upstream command stats currently.
      bool latency_in_micros = 4;
      Specified by:
      getLatencyInMicros in interface RedisProxyOrBuilder
      Returns:
      The latencyInMicros.

    • setLatencyInMicros

      public RedisProxy.Builder setLatencyInMicros(boolean value)
       Indicates that latency stat should be computed in microseconds. By default it is computed in
 milliseconds. This does not apply to upstream command stats currently.
      bool latency_in_micros = 4;
      Parameters:
      value - The latencyInMicros to set.
      Returns:
      This builder for chaining.

    • clearLatencyInMicros

      public RedisProxy.Builder clearLatencyInMicros()
       Indicates that latency stat should be computed in microseconds. By default it is computed in
 milliseconds. This does not apply to upstream command stats currently.
      bool latency_in_micros = 4;
      Returns:
      This builder for chaining.

    • hasPrefixRoutes

      public boolean hasPrefixRoutes()
       List of **unique** prefixes used to separate keys from different workloads to different
 clusters. Envoy will always favor the longest match first in case of overlap. A catch-all
 cluster can be used to forward commands when there is no match. Time complexity of the
 lookups are in O(min(longest key prefix, key length)).

 Example:

 .. code-block:: yaml

    prefix_routes:
      routes:
        - prefix: "ab"
          cluster: "cluster_a"
        - prefix: "abc"
          cluster: "cluster_b"

 When using the above routes, the following prefixes would be sent to:

 * ``get abc:users`` would retrieve the key 'abc:users' from cluster_b.
 * ``get ab:users`` would retrieve the key 'ab:users' from cluster_a.
 * ``get z:users`` would return a NoUpstreamHost error. A :ref:`catch-all
   route<envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes.catch_all_route>`
   would have retrieved the key from that cluster instead.

 See the :ref:`configuration section
 <arch_overview_redis_configuration>` of the architecture overview for recommendations on
 configuring the backing clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes prefix_routes = 5;
      Specified by:
      hasPrefixRoutes in interface RedisProxyOrBuilder
      Returns:
      Whether the prefixRoutes field is set.

    • getPrefixRoutes

      public RedisProxy.PrefixRoutes getPrefixRoutes()
       List of **unique** prefixes used to separate keys from different workloads to different
 clusters. Envoy will always favor the longest match first in case of overlap. A catch-all
 cluster can be used to forward commands when there is no match. Time complexity of the
 lookups are in O(min(longest key prefix, key length)).

 Example:

 .. code-block:: yaml

    prefix_routes:
      routes:
        - prefix: "ab"
          cluster: "cluster_a"
        - prefix: "abc"
          cluster: "cluster_b"

 When using the above routes, the following prefixes would be sent to:

 * ``get abc:users`` would retrieve the key 'abc:users' from cluster_b.
 * ``get ab:users`` would retrieve the key 'ab:users' from cluster_a.
 * ``get z:users`` would return a NoUpstreamHost error. A :ref:`catch-all
   route<envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes.catch_all_route>`
   would have retrieved the key from that cluster instead.

 See the :ref:`configuration section
 <arch_overview_redis_configuration>` of the architecture overview for recommendations on
 configuring the backing clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes prefix_routes = 5;
      Specified by:
      getPrefixRoutes in interface RedisProxyOrBuilder
      Returns:
      The prefixRoutes.

    • setPrefixRoutes

      public RedisProxy.Builder setPrefixRoutes(RedisProxy.PrefixRoutes value)
       List of **unique** prefixes used to separate keys from different workloads to different
 clusters. Envoy will always favor the longest match first in case of overlap. A catch-all
 cluster can be used to forward commands when there is no match. Time complexity of the
 lookups are in O(min(longest key prefix, key length)).

 Example:

 .. code-block:: yaml

    prefix_routes:
      routes:
        - prefix: "ab"
          cluster: "cluster_a"
        - prefix: "abc"
          cluster: "cluster_b"

 When using the above routes, the following prefixes would be sent to:

 * ``get abc:users`` would retrieve the key 'abc:users' from cluster_b.
 * ``get ab:users`` would retrieve the key 'ab:users' from cluster_a.
 * ``get z:users`` would return a NoUpstreamHost error. A :ref:`catch-all
   route<envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes.catch_all_route>`
   would have retrieved the key from that cluster instead.

 See the :ref:`configuration section
 <arch_overview_redis_configuration>` of the architecture overview for recommendations on
 configuring the backing clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes prefix_routes = 5;

    • setPrefixRoutes

      public RedisProxy.Builder setPrefixRoutes(RedisProxy.PrefixRoutes.Builder builderForValue)
       List of **unique** prefixes used to separate keys from different workloads to different
 clusters. Envoy will always favor the longest match first in case of overlap. A catch-all
 cluster can be used to forward commands when there is no match. Time complexity of the
 lookups are in O(min(longest key prefix, key length)).

 Example:

 .. code-block:: yaml

    prefix_routes:
      routes:
        - prefix: "ab"
          cluster: "cluster_a"
        - prefix: "abc"
          cluster: "cluster_b"

 When using the above routes, the following prefixes would be sent to:

 * ``get abc:users`` would retrieve the key 'abc:users' from cluster_b.
 * ``get ab:users`` would retrieve the key 'ab:users' from cluster_a.
 * ``get z:users`` would return a NoUpstreamHost error. A :ref:`catch-all
   route<envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes.catch_all_route>`
   would have retrieved the key from that cluster instead.

 See the :ref:`configuration section
 <arch_overview_redis_configuration>` of the architecture overview for recommendations on
 configuring the backing clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes prefix_routes = 5;

    • mergePrefixRoutes

      public RedisProxy.Builder mergePrefixRoutes(RedisProxy.PrefixRoutes value)
       List of **unique** prefixes used to separate keys from different workloads to different
 clusters. Envoy will always favor the longest match first in case of overlap. A catch-all
 cluster can be used to forward commands when there is no match. Time complexity of the
 lookups are in O(min(longest key prefix, key length)).

 Example:

 .. code-block:: yaml

    prefix_routes:
      routes:
        - prefix: "ab"
          cluster: "cluster_a"
        - prefix: "abc"
          cluster: "cluster_b"

 When using the above routes, the following prefixes would be sent to:

 * ``get abc:users`` would retrieve the key 'abc:users' from cluster_b.
 * ``get ab:users`` would retrieve the key 'ab:users' from cluster_a.
 * ``get z:users`` would return a NoUpstreamHost error. A :ref:`catch-all
   route<envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes.catch_all_route>`
   would have retrieved the key from that cluster instead.

 See the :ref:`configuration section
 <arch_overview_redis_configuration>` of the architecture overview for recommendations on
 configuring the backing clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes prefix_routes = 5;

    • clearPrefixRoutes

      public RedisProxy.Builder clearPrefixRoutes()
       List of **unique** prefixes used to separate keys from different workloads to different
 clusters. Envoy will always favor the longest match first in case of overlap. A catch-all
 cluster can be used to forward commands when there is no match. Time complexity of the
 lookups are in O(min(longest key prefix, key length)).

 Example:

 .. code-block:: yaml

    prefix_routes:
      routes:
        - prefix: "ab"
          cluster: "cluster_a"
        - prefix: "abc"
          cluster: "cluster_b"

 When using the above routes, the following prefixes would be sent to:

 * ``get abc:users`` would retrieve the key 'abc:users' from cluster_b.
 * ``get ab:users`` would retrieve the key 'ab:users' from cluster_a.
 * ``get z:users`` would return a NoUpstreamHost error. A :ref:`catch-all
   route<envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes.catch_all_route>`
   would have retrieved the key from that cluster instead.

 See the :ref:`configuration section
 <arch_overview_redis_configuration>` of the architecture overview for recommendations on
 configuring the backing clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes prefix_routes = 5;

    • getPrefixRoutesBuilder

      public RedisProxy.PrefixRoutes.Builder getPrefixRoutesBuilder()
       List of **unique** prefixes used to separate keys from different workloads to different
 clusters. Envoy will always favor the longest match first in case of overlap. A catch-all
 cluster can be used to forward commands when there is no match. Time complexity of the
 lookups are in O(min(longest key prefix, key length)).

 Example:

 .. code-block:: yaml

    prefix_routes:
      routes:
        - prefix: "ab"
          cluster: "cluster_a"
        - prefix: "abc"
          cluster: "cluster_b"

 When using the above routes, the following prefixes would be sent to:

 * ``get abc:users`` would retrieve the key 'abc:users' from cluster_b.
 * ``get ab:users`` would retrieve the key 'ab:users' from cluster_a.
 * ``get z:users`` would return a NoUpstreamHost error. A :ref:`catch-all
   route<envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes.catch_all_route>`
   would have retrieved the key from that cluster instead.

 See the :ref:`configuration section
 <arch_overview_redis_configuration>` of the architecture overview for recommendations on
 configuring the backing clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes prefix_routes = 5;

    • getPrefixRoutesOrBuilder

      public RedisProxy.PrefixRoutesOrBuilder getPrefixRoutesOrBuilder()
       List of **unique** prefixes used to separate keys from different workloads to different
 clusters. Envoy will always favor the longest match first in case of overlap. A catch-all
 cluster can be used to forward commands when there is no match. Time complexity of the
 lookups are in O(min(longest key prefix, key length)).

 Example:

 .. code-block:: yaml

    prefix_routes:
      routes:
        - prefix: "ab"
          cluster: "cluster_a"
        - prefix: "abc"
          cluster: "cluster_b"

 When using the above routes, the following prefixes would be sent to:

 * ``get abc:users`` would retrieve the key 'abc:users' from cluster_b.
 * ``get ab:users`` would retrieve the key 'ab:users' from cluster_a.
 * ``get z:users`` would return a NoUpstreamHost error. A :ref:`catch-all
   route<envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes.catch_all_route>`
   would have retrieved the key from that cluster instead.

 See the :ref:`configuration section
 <arch_overview_redis_configuration>` of the architecture overview for recommendations on
 configuring the backing clusters.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.PrefixRoutes prefix_routes = 5;
      Specified by:
      getPrefixRoutesOrBuilder in interface RedisProxyOrBuilder

    • hasDownstreamAuthPassword

      @Deprecated public boolean hasDownstreamAuthPassword()
      Deprecated.
      envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.downstream_auth_password is deprecated. See envoy/extensions/filters/network/redis_proxy/v3/redis_proxy.proto;l=301
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this password before enabling any other
 command. If an AUTH command's password matches this password, an "OK" response will be returned
 to the client. If the AUTH command password does not match this password, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.

 .. attention::
   This field is deprecated. Use :ref:`downstream_auth_passwords
   <envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.downstream_auth_passwords>`.
      .envoy.config.core.v3.DataSource downstream_auth_password = 6 [deprecated = true, (.udpa.annotations.sensitive) = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      Specified by:
      hasDownstreamAuthPassword in interface RedisProxyOrBuilder
      Returns:
      Whether the downstreamAuthPassword field is set.

    • getDownstreamAuthPassword

      @Deprecated public DataSource getDownstreamAuthPassword()
      Deprecated.
      envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.downstream_auth_password is deprecated. See envoy/extensions/filters/network/redis_proxy/v3/redis_proxy.proto;l=301
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this password before enabling any other
 command. If an AUTH command's password matches this password, an "OK" response will be returned
 to the client. If the AUTH command password does not match this password, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.

 .. attention::
   This field is deprecated. Use :ref:`downstream_auth_passwords
   <envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.downstream_auth_passwords>`.
      .envoy.config.core.v3.DataSource downstream_auth_password = 6 [deprecated = true, (.udpa.annotations.sensitive) = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      Specified by:
      getDownstreamAuthPassword in interface RedisProxyOrBuilder
      Returns:
      The downstreamAuthPassword.

    • setDownstreamAuthPassword

      @Deprecated public RedisProxy.Builder setDownstreamAuthPassword(DataSource value)
      Deprecated.
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this password before enabling any other
 command. If an AUTH command's password matches this password, an "OK" response will be returned
 to the client. If the AUTH command password does not match this password, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.

 .. attention::
   This field is deprecated. Use :ref:`downstream_auth_passwords
   <envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.downstream_auth_passwords>`.
      .envoy.config.core.v3.DataSource downstream_auth_password = 6 [deprecated = true, (.udpa.annotations.sensitive) = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];

    • setDownstreamAuthPassword

      @Deprecated public RedisProxy.Builder setDownstreamAuthPassword(DataSource.Builder builderForValue)
      Deprecated.
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this password before enabling any other
 command. If an AUTH command's password matches this password, an "OK" response will be returned
 to the client. If the AUTH command password does not match this password, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.

 .. attention::
   This field is deprecated. Use :ref:`downstream_auth_passwords
   <envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.downstream_auth_passwords>`.
      .envoy.config.core.v3.DataSource downstream_auth_password = 6 [deprecated = true, (.udpa.annotations.sensitive) = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];

    • mergeDownstreamAuthPassword

      @Deprecated public RedisProxy.Builder mergeDownstreamAuthPassword(DataSource value)
      Deprecated.
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this password before enabling any other
 command. If an AUTH command's password matches this password, an "OK" response will be returned
 to the client. If the AUTH command password does not match this password, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.

 .. attention::
   This field is deprecated. Use :ref:`downstream_auth_passwords
   <envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.downstream_auth_passwords>`.
      .envoy.config.core.v3.DataSource downstream_auth_password = 6 [deprecated = true, (.udpa.annotations.sensitive) = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];

    • clearDownstreamAuthPassword

      @Deprecated public RedisProxy.Builder clearDownstreamAuthPassword()
      Deprecated.
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this password before enabling any other
 command. If an AUTH command's password matches this password, an "OK" response will be returned
 to the client. If the AUTH command password does not match this password, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.

 .. attention::
   This field is deprecated. Use :ref:`downstream_auth_passwords
   <envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.downstream_auth_passwords>`.
      .envoy.config.core.v3.DataSource downstream_auth_password = 6 [deprecated = true, (.udpa.annotations.sensitive) = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];

    • getDownstreamAuthPasswordBuilder

      @Deprecated public DataSource.Builder getDownstreamAuthPasswordBuilder()
      Deprecated.
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this password before enabling any other
 command. If an AUTH command's password matches this password, an "OK" response will be returned
 to the client. If the AUTH command password does not match this password, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.

 .. attention::
   This field is deprecated. Use :ref:`downstream_auth_passwords
   <envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.downstream_auth_passwords>`.
      .envoy.config.core.v3.DataSource downstream_auth_password = 6 [deprecated = true, (.udpa.annotations.sensitive) = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];

    • getDownstreamAuthPasswordOrBuilder

      @Deprecated public DataSourceOrBuilder getDownstreamAuthPasswordOrBuilder()
      Deprecated.
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this password before enabling any other
 command. If an AUTH command's password matches this password, an "OK" response will be returned
 to the client. If the AUTH command password does not match this password, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.

 .. attention::
   This field is deprecated. Use :ref:`downstream_auth_passwords
   <envoy_v3_api_field_extensions.filters.network.redis_proxy.v3.RedisProxy.downstream_auth_passwords>`.
      .envoy.config.core.v3.DataSource downstream_auth_password = 6 [deprecated = true, (.udpa.annotations.sensitive) = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      Specified by:
      getDownstreamAuthPasswordOrBuilder in interface RedisProxyOrBuilder

    • getDownstreamAuthPasswordsList

      public List<DataSource> getDownstreamAuthPasswordsList()
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];
      Specified by:
      getDownstreamAuthPasswordsList in interface RedisProxyOrBuilder

    • getDownstreamAuthPasswordsCount

      public int getDownstreamAuthPasswordsCount()
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];
      Specified by:
      getDownstreamAuthPasswordsCount in interface RedisProxyOrBuilder

    • getDownstreamAuthPasswords

      public DataSource getDownstreamAuthPasswords(int index)
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];
      Specified by:
      getDownstreamAuthPasswords in interface RedisProxyOrBuilder

    • setDownstreamAuthPasswords

      public RedisProxy.Builder setDownstreamAuthPasswords(int index, DataSource value)
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • setDownstreamAuthPasswords

      public RedisProxy.Builder setDownstreamAuthPasswords(int index, DataSource.Builder builderForValue)
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • addDownstreamAuthPasswords

      public RedisProxy.Builder addDownstreamAuthPasswords(DataSource value)
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • addDownstreamAuthPasswords

      public RedisProxy.Builder addDownstreamAuthPasswords(int index, DataSource value)
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • addDownstreamAuthPasswords

      public RedisProxy.Builder addDownstreamAuthPasswords(DataSource.Builder builderForValue)
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • addDownstreamAuthPasswords

      public RedisProxy.Builder addDownstreamAuthPasswords(int index, DataSource.Builder builderForValue)
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • addAllDownstreamAuthPasswords

      public RedisProxy.Builder addAllDownstreamAuthPasswords(Iterable<? extends DataSource> values)
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • clearDownstreamAuthPasswords

      public RedisProxy.Builder clearDownstreamAuthPasswords()
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • removeDownstreamAuthPasswords

      public RedisProxy.Builder removeDownstreamAuthPasswords(int index)
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • getDownstreamAuthPasswordsBuilder

      public DataSource.Builder getDownstreamAuthPasswordsBuilder(int index)
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • getDownstreamAuthPasswordsOrBuilder

      public DataSourceOrBuilder getDownstreamAuthPasswordsOrBuilder(int index)
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];
      Specified by:
      getDownstreamAuthPasswordsOrBuilder in interface RedisProxyOrBuilder

    • getDownstreamAuthPasswordsOrBuilderList

      public List<? extends DataSourceOrBuilder> getDownstreamAuthPasswordsOrBuilderList()
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];
      Specified by:
      getDownstreamAuthPasswordsOrBuilderList in interface RedisProxyOrBuilder

    • addDownstreamAuthPasswordsBuilder

      public DataSource.Builder addDownstreamAuthPasswordsBuilder()
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • addDownstreamAuthPasswordsBuilder

      public DataSource.Builder addDownstreamAuthPasswordsBuilder(int index)
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • getDownstreamAuthPasswordsBuilderList

      public List<DataSource.Builder> getDownstreamAuthPasswordsBuilderList()
       Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with one of these passwords before enabling any other
 command. If an AUTH command's password matches one of these passwords, an "OK" response will be returned
 to the client. If the AUTH command password does not match, then an "ERR invalid
 password" error will be returned. If any other command is received before AUTH when the
 password(s) are set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no password is set" error will be returned.
      repeated .envoy.config.core.v3.DataSource downstream_auth_passwords = 9 [(.udpa.annotations.sensitive) = true];

    • getFaultsList

      public List<RedisProxy.RedisFault> getFaultsList()
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;
      Specified by:
      getFaultsList in interface RedisProxyOrBuilder

    • getFaultsCount

      public int getFaultsCount()
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;
      Specified by:
      getFaultsCount in interface RedisProxyOrBuilder

    • getFaults

      public RedisProxy.RedisFault getFaults(int index)
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;
      Specified by:
      getFaults in interface RedisProxyOrBuilder

    • setFaults

      public RedisProxy.Builder setFaults(int index, RedisProxy.RedisFault value)
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • setFaults

      public RedisProxy.Builder setFaults(int index, RedisProxy.RedisFault.Builder builderForValue)
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • addFaults

      public RedisProxy.Builder addFaults(RedisProxy.RedisFault value)
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • addFaults

      public RedisProxy.Builder addFaults(int index, RedisProxy.RedisFault value)
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • addFaults

      public RedisProxy.Builder addFaults(RedisProxy.RedisFault.Builder builderForValue)
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • addFaults

      public RedisProxy.Builder addFaults(int index, RedisProxy.RedisFault.Builder builderForValue)
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • addAllFaults

      public RedisProxy.Builder addAllFaults(Iterable<? extends RedisProxy.RedisFault> values)
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • clearFaults

      public RedisProxy.Builder clearFaults()
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • removeFaults

      public RedisProxy.Builder removeFaults(int index)
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • getFaultsBuilder

      public RedisProxy.RedisFault.Builder getFaultsBuilder(int index)
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • getFaultsOrBuilder

      public RedisProxy.RedisFaultOrBuilder getFaultsOrBuilder(int index)
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;
      Specified by:
      getFaultsOrBuilder in interface RedisProxyOrBuilder

    • getFaultsOrBuilderList

      public List<? extends RedisProxy.RedisFaultOrBuilder> getFaultsOrBuilderList()
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;
      Specified by:
      getFaultsOrBuilderList in interface RedisProxyOrBuilder

    • addFaultsBuilder

      public RedisProxy.RedisFault.Builder addFaultsBuilder()
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • addFaultsBuilder

      public RedisProxy.RedisFault.Builder addFaultsBuilder(int index)
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • getFaultsBuilderList

      public List<RedisProxy.RedisFault.Builder> getFaultsBuilderList()
       List of faults to inject. Faults currently come in two flavors:
 - Delay, which delays a request.
 - Error, which responds to a request with an error. Errors can also have delays attached.

 Example:

 .. code-block:: yaml

    faults:
    - fault_type: ERROR
      fault_enabled:
        default_value:
          numerator: 10
          denominator: HUNDRED
        runtime_key: "bogus_key"
        commands:
        - GET
      - fault_type: DELAY
        fault_enabled:
          default_value:
            numerator: 10
            denominator: HUNDRED
          runtime_key: "bogus_key"
        delay: 2s

 See the :ref:`fault injection section
 <config_network_filters_redis_proxy_fault_injection>` for more information on how to configure this.
      repeated .envoy.extensions.filters.network.redis_proxy.v3.RedisProxy.RedisFault faults = 8;

    • hasDownstreamAuthUsername

      public boolean hasDownstreamAuthUsername()
       If a username is provided an ACL style AUTH command will be required with a username and password.
 Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this username and the ``downstream_auth_password``
 before enabling any other command. If an AUTH command's username and password matches this username
 and the ``downstream_auth_password`` , an "OK" response will be returned to the client. If the AUTH
 command username or password does not match this username or the ``downstream_auth_password``, then an
 "WRONGPASS invalid username-password pair" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no ACL is set" error will be returned.
      .envoy.config.core.v3.DataSource downstream_auth_username = 7 [(.udpa.annotations.sensitive) = true];
      Specified by:
      hasDownstreamAuthUsername in interface RedisProxyOrBuilder
      Returns:
      Whether the downstreamAuthUsername field is set.

    • getDownstreamAuthUsername

      public DataSource getDownstreamAuthUsername()
       If a username is provided an ACL style AUTH command will be required with a username and password.
 Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this username and the ``downstream_auth_password``
 before enabling any other command. If an AUTH command's username and password matches this username
 and the ``downstream_auth_password`` , an "OK" response will be returned to the client. If the AUTH
 command username or password does not match this username or the ``downstream_auth_password``, then an
 "WRONGPASS invalid username-password pair" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no ACL is set" error will be returned.
      .envoy.config.core.v3.DataSource downstream_auth_username = 7 [(.udpa.annotations.sensitive) = true];
      Specified by:
      getDownstreamAuthUsername in interface RedisProxyOrBuilder
      Returns:
      The downstreamAuthUsername.

    • setDownstreamAuthUsername

      public RedisProxy.Builder setDownstreamAuthUsername(DataSource value)
       If a username is provided an ACL style AUTH command will be required with a username and password.
 Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this username and the ``downstream_auth_password``
 before enabling any other command. If an AUTH command's username and password matches this username
 and the ``downstream_auth_password`` , an "OK" response will be returned to the client. If the AUTH
 command username or password does not match this username or the ``downstream_auth_password``, then an
 "WRONGPASS invalid username-password pair" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no ACL is set" error will be returned.
      .envoy.config.core.v3.DataSource downstream_auth_username = 7 [(.udpa.annotations.sensitive) = true];

    • setDownstreamAuthUsername

      public RedisProxy.Builder setDownstreamAuthUsername(DataSource.Builder builderForValue)
       If a username is provided an ACL style AUTH command will be required with a username and password.
 Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this username and the ``downstream_auth_password``
 before enabling any other command. If an AUTH command's username and password matches this username
 and the ``downstream_auth_password`` , an "OK" response will be returned to the client. If the AUTH
 command username or password does not match this username or the ``downstream_auth_password``, then an
 "WRONGPASS invalid username-password pair" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no ACL is set" error will be returned.
      .envoy.config.core.v3.DataSource downstream_auth_username = 7 [(.udpa.annotations.sensitive) = true];

    • mergeDownstreamAuthUsername

      public RedisProxy.Builder mergeDownstreamAuthUsername(DataSource value)
       If a username is provided an ACL style AUTH command will be required with a username and password.
 Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this username and the ``downstream_auth_password``
 before enabling any other command. If an AUTH command's username and password matches this username
 and the ``downstream_auth_password`` , an "OK" response will be returned to the client. If the AUTH
 command username or password does not match this username or the ``downstream_auth_password``, then an
 "WRONGPASS invalid username-password pair" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no ACL is set" error will be returned.
      .envoy.config.core.v3.DataSource downstream_auth_username = 7 [(.udpa.annotations.sensitive) = true];

    • clearDownstreamAuthUsername

      public RedisProxy.Builder clearDownstreamAuthUsername()
       If a username is provided an ACL style AUTH command will be required with a username and password.
 Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this username and the ``downstream_auth_password``
 before enabling any other command. If an AUTH command's username and password matches this username
 and the ``downstream_auth_password`` , an "OK" response will be returned to the client. If the AUTH
 command username or password does not match this username or the ``downstream_auth_password``, then an
 "WRONGPASS invalid username-password pair" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no ACL is set" error will be returned.
      .envoy.config.core.v3.DataSource downstream_auth_username = 7 [(.udpa.annotations.sensitive) = true];

    • getDownstreamAuthUsernameBuilder

      public DataSource.Builder getDownstreamAuthUsernameBuilder()
       If a username is provided an ACL style AUTH command will be required with a username and password.
 Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this username and the ``downstream_auth_password``
 before enabling any other command. If an AUTH command's username and password matches this username
 and the ``downstream_auth_password`` , an "OK" response will be returned to the client. If the AUTH
 command username or password does not match this username or the ``downstream_auth_password``, then an
 "WRONGPASS invalid username-password pair" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no ACL is set" error will be returned.
      .envoy.config.core.v3.DataSource downstream_auth_username = 7 [(.udpa.annotations.sensitive) = true];

    • getDownstreamAuthUsernameOrBuilder

      public DataSourceOrBuilder getDownstreamAuthUsernameOrBuilder()
       If a username is provided an ACL style AUTH command will be required with a username and password.
 Authenticate Redis client connections locally by forcing downstream clients to issue a `Redis
 AUTH command <https://redis.io/commands/auth>`_ with this username and the ``downstream_auth_password``
 before enabling any other command. If an AUTH command's username and password matches this username
 and the ``downstream_auth_password`` , an "OK" response will be returned to the client. If the AUTH
 command username or password does not match this username or the ``downstream_auth_password``, then an
 "WRONGPASS invalid username-password pair" error will be returned. If any other command is received before AUTH when this
 password is set, then a "NOAUTH Authentication required." error response will be sent to the
 client. If an AUTH command is received when the password is not set, then an "ERR Client sent
 AUTH, but no ACL is set" error will be returned.
      .envoy.config.core.v3.DataSource downstream_auth_username = 7 [(.udpa.annotations.sensitive) = true];
      Specified by:
      getDownstreamAuthUsernameOrBuilder in interface RedisProxyOrBuilder

    • hasExternalAuthProvider

      public boolean hasExternalAuthProvider()
       External authentication configuration. If set, instead of validating username and password against ``downstream_auth_username`` and ``downstream_auth_password``,
 the filter will call an external gRPC service to authenticate the client.
 A typical usage of this feature is for situations where the password is a one-time token that needs to be validated against a remote service, like a sidecar.
 Expiration is also supported, which will disable any further commands from the client after the expiration time, unless a new AUTH command is received and the external auth service returns a new expiration time.
 If the external auth service returns an error, authentication is considered failed.
 If this setting is set together with ``downstream_auth_username`` and ``downstream_auth_password``, the external auth service will be source of truth, but those fields will still be used for downstream authentication to the cluster.
 The API is defined by :ref:`RedisProxyExternalAuthRequest <envoy_v3_api_msg_service.redis_auth.v3.RedisProxyExternalAuthRequest>`.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisExternalAuthProvider external_auth_provider = 10;
      Specified by:
      hasExternalAuthProvider in interface RedisProxyOrBuilder
      Returns:
      Whether the externalAuthProvider field is set.

    • getExternalAuthProvider

      public RedisExternalAuthProvider getExternalAuthProvider()
       External authentication configuration. If set, instead of validating username and password against ``downstream_auth_username`` and ``downstream_auth_password``,
 the filter will call an external gRPC service to authenticate the client.
 A typical usage of this feature is for situations where the password is a one-time token that needs to be validated against a remote service, like a sidecar.
 Expiration is also supported, which will disable any further commands from the client after the expiration time, unless a new AUTH command is received and the external auth service returns a new expiration time.
 If the external auth service returns an error, authentication is considered failed.
 If this setting is set together with ``downstream_auth_username`` and ``downstream_auth_password``, the external auth service will be source of truth, but those fields will still be used for downstream authentication to the cluster.
 The API is defined by :ref:`RedisProxyExternalAuthRequest <envoy_v3_api_msg_service.redis_auth.v3.RedisProxyExternalAuthRequest>`.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisExternalAuthProvider external_auth_provider = 10;
      Specified by:
      getExternalAuthProvider in interface RedisProxyOrBuilder
      Returns:
      The externalAuthProvider.

    • setExternalAuthProvider

      public RedisProxy.Builder setExternalAuthProvider(RedisExternalAuthProvider value)
       External authentication configuration. If set, instead of validating username and password against ``downstream_auth_username`` and ``downstream_auth_password``,
 the filter will call an external gRPC service to authenticate the client.
 A typical usage of this feature is for situations where the password is a one-time token that needs to be validated against a remote service, like a sidecar.
 Expiration is also supported, which will disable any further commands from the client after the expiration time, unless a new AUTH command is received and the external auth service returns a new expiration time.
 If the external auth service returns an error, authentication is considered failed.
 If this setting is set together with ``downstream_auth_username`` and ``downstream_auth_password``, the external auth service will be source of truth, but those fields will still be used for downstream authentication to the cluster.
 The API is defined by :ref:`RedisProxyExternalAuthRequest <envoy_v3_api_msg_service.redis_auth.v3.RedisProxyExternalAuthRequest>`.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisExternalAuthProvider external_auth_provider = 10;

    • setExternalAuthProvider

      public RedisProxy.Builder setExternalAuthProvider(RedisExternalAuthProvider.Builder builderForValue)
       External authentication configuration. If set, instead of validating username and password against ``downstream_auth_username`` and ``downstream_auth_password``,
 the filter will call an external gRPC service to authenticate the client.
 A typical usage of this feature is for situations where the password is a one-time token that needs to be validated against a remote service, like a sidecar.
 Expiration is also supported, which will disable any further commands from the client after the expiration time, unless a new AUTH command is received and the external auth service returns a new expiration time.
 If the external auth service returns an error, authentication is considered failed.
 If this setting is set together with ``downstream_auth_username`` and ``downstream_auth_password``, the external auth service will be source of truth, but those fields will still be used for downstream authentication to the cluster.
 The API is defined by :ref:`RedisProxyExternalAuthRequest <envoy_v3_api_msg_service.redis_auth.v3.RedisProxyExternalAuthRequest>`.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisExternalAuthProvider external_auth_provider = 10;

    • mergeExternalAuthProvider

      public RedisProxy.Builder mergeExternalAuthProvider(RedisExternalAuthProvider value)
       External authentication configuration. If set, instead of validating username and password against ``downstream_auth_username`` and ``downstream_auth_password``,
 the filter will call an external gRPC service to authenticate the client.
 A typical usage of this feature is for situations where the password is a one-time token that needs to be validated against a remote service, like a sidecar.
 Expiration is also supported, which will disable any further commands from the client after the expiration time, unless a new AUTH command is received and the external auth service returns a new expiration time.
 If the external auth service returns an error, authentication is considered failed.
 If this setting is set together with ``downstream_auth_username`` and ``downstream_auth_password``, the external auth service will be source of truth, but those fields will still be used for downstream authentication to the cluster.
 The API is defined by :ref:`RedisProxyExternalAuthRequest <envoy_v3_api_msg_service.redis_auth.v3.RedisProxyExternalAuthRequest>`.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisExternalAuthProvider external_auth_provider = 10;

    • clearExternalAuthProvider

      public RedisProxy.Builder clearExternalAuthProvider()
       External authentication configuration. If set, instead of validating username and password against ``downstream_auth_username`` and ``downstream_auth_password``,
 the filter will call an external gRPC service to authenticate the client.
 A typical usage of this feature is for situations where the password is a one-time token that needs to be validated against a remote service, like a sidecar.
 Expiration is also supported, which will disable any further commands from the client after the expiration time, unless a new AUTH command is received and the external auth service returns a new expiration time.
 If the external auth service returns an error, authentication is considered failed.
 If this setting is set together with ``downstream_auth_username`` and ``downstream_auth_password``, the external auth service will be source of truth, but those fields will still be used for downstream authentication to the cluster.
 The API is defined by :ref:`RedisProxyExternalAuthRequest <envoy_v3_api_msg_service.redis_auth.v3.RedisProxyExternalAuthRequest>`.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisExternalAuthProvider external_auth_provider = 10;

    • getExternalAuthProviderBuilder

      public RedisExternalAuthProvider.Builder getExternalAuthProviderBuilder()
       External authentication configuration. If set, instead of validating username and password against ``downstream_auth_username`` and ``downstream_auth_password``,
 the filter will call an external gRPC service to authenticate the client.
 A typical usage of this feature is for situations where the password is a one-time token that needs to be validated against a remote service, like a sidecar.
 Expiration is also supported, which will disable any further commands from the client after the expiration time, unless a new AUTH command is received and the external auth service returns a new expiration time.
 If the external auth service returns an error, authentication is considered failed.
 If this setting is set together with ``downstream_auth_username`` and ``downstream_auth_password``, the external auth service will be source of truth, but those fields will still be used for downstream authentication to the cluster.
 The API is defined by :ref:`RedisProxyExternalAuthRequest <envoy_v3_api_msg_service.redis_auth.v3.RedisProxyExternalAuthRequest>`.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisExternalAuthProvider external_auth_provider = 10;

    • getExternalAuthProviderOrBuilder

      public RedisExternalAuthProviderOrBuilder getExternalAuthProviderOrBuilder()
       External authentication configuration. If set, instead of validating username and password against ``downstream_auth_username`` and ``downstream_auth_password``,
 the filter will call an external gRPC service to authenticate the client.
 A typical usage of this feature is for situations where the password is a one-time token that needs to be validated against a remote service, like a sidecar.
 Expiration is also supported, which will disable any further commands from the client after the expiration time, unless a new AUTH command is received and the external auth service returns a new expiration time.
 If the external auth service returns an error, authentication is considered failed.
 If this setting is set together with ``downstream_auth_username`` and ``downstream_auth_password``, the external auth service will be source of truth, but those fields will still be used for downstream authentication to the cluster.
 The API is defined by :ref:`RedisProxyExternalAuthRequest <envoy_v3_api_msg_service.redis_auth.v3.RedisProxyExternalAuthRequest>`.
      .envoy.extensions.filters.network.redis_proxy.v3.RedisExternalAuthProvider external_auth_provider = 10;
      Specified by:
      getExternalAuthProviderOrBuilder in interface RedisProxyOrBuilder

    • getCustomCommandsList

      public com.google.protobuf.ProtocolStringList getCustomCommandsList()
       Optional configure redis custom commands for the proxy, eg -> ["my_custom_cmd1", "my_custom_cmd2"]

 .. note::
   The is to support redis's feature wherein new commands can be added using redis' modules api:
   https://redis.io/docs/latest/develop/reference/modules/
      repeated string custom_commands = 11;
      Specified by:
      getCustomCommandsList in interface RedisProxyOrBuilder
      Returns:
      A list containing the customCommands.

    • getCustomCommandsCount

      public int getCustomCommandsCount()
       Optional configure redis custom commands for the proxy, eg -> ["my_custom_cmd1", "my_custom_cmd2"]

 .. note::
   The is to support redis's feature wherein new commands can be added using redis' modules api:
   https://redis.io/docs/latest/develop/reference/modules/
      repeated string custom_commands = 11;
      Specified by:
      getCustomCommandsCount in interface RedisProxyOrBuilder
      Returns:
      The count of customCommands.

    • getCustomCommands

      public String getCustomCommands(int index)
       Optional configure redis custom commands for the proxy, eg -> ["my_custom_cmd1", "my_custom_cmd2"]

 .. note::
   The is to support redis's feature wherein new commands can be added using redis' modules api:
   https://redis.io/docs/latest/develop/reference/modules/
      repeated string custom_commands = 11;
      Specified by:
      getCustomCommands in interface RedisProxyOrBuilder
      Parameters:
      index - The index of the element to return.
      Returns:
      The customCommands at the given index.

    • getCustomCommandsBytes

      public com.google.protobuf.ByteString getCustomCommandsBytes(int index)
       Optional configure redis custom commands for the proxy, eg -> ["my_custom_cmd1", "my_custom_cmd2"]

 .. note::
   The is to support redis's feature wherein new commands can be added using redis' modules api:
   https://redis.io/docs/latest/develop/reference/modules/
      repeated string custom_commands = 11;
      Specified by:
      getCustomCommandsBytes in interface RedisProxyOrBuilder
      Parameters:
      index - The index of the value to return.
      Returns:
      The bytes of the customCommands at the given index.

    • setCustomCommands

      public RedisProxy.Builder setCustomCommands(int index, String value)
       Optional configure redis custom commands for the proxy, eg -> ["my_custom_cmd1", "my_custom_cmd2"]

 .. note::
   The is to support redis's feature wherein new commands can be added using redis' modules api:
   https://redis.io/docs/latest/develop/reference/modules/
      repeated string custom_commands = 11;
      Parameters:
      index - The index to set the value at.
      value - The customCommands to set.
      Returns:
      This builder for chaining.

    • addCustomCommands

      public RedisProxy.Builder addCustomCommands(String value)
       Optional configure redis custom commands for the proxy, eg -> ["my_custom_cmd1", "my_custom_cmd2"]

 .. note::
   The is to support redis's feature wherein new commands can be added using redis' modules api:
   https://redis.io/docs/latest/develop/reference/modules/
      repeated string custom_commands = 11;
      Parameters:
      value - The customCommands to add.
      Returns:
      This builder for chaining.

    • addAllCustomCommands

      public RedisProxy.Builder addAllCustomCommands(Iterable<String> values)
       Optional configure redis custom commands for the proxy, eg -> ["my_custom_cmd1", "my_custom_cmd2"]

 .. note::
   The is to support redis's feature wherein new commands can be added using redis' modules api:
   https://redis.io/docs/latest/develop/reference/modules/
      repeated string custom_commands = 11;
      Parameters:
      values - The customCommands to add.
      Returns:
      This builder for chaining.

    • clearCustomCommands

      public RedisProxy.Builder clearCustomCommands()
       Optional configure redis custom commands for the proxy, eg -> ["my_custom_cmd1", "my_custom_cmd2"]

 .. note::
   The is to support redis's feature wherein new commands can be added using redis' modules api:
   https://redis.io/docs/latest/develop/reference/modules/
      repeated string custom_commands = 11;
      Returns:
      This builder for chaining.

    • addCustomCommandsBytes

      public RedisProxy.Builder addCustomCommandsBytes(com.google.protobuf.ByteString value)
       Optional configure redis custom commands for the proxy, eg -> ["my_custom_cmd1", "my_custom_cmd2"]

 .. note::
   The is to support redis's feature wherein new commands can be added using redis' modules api:
   https://redis.io/docs/latest/develop/reference/modules/
      repeated string custom_commands = 11;
      Parameters:
      value - The bytes of the customCommands to add.
      Returns:
      This builder for chaining.

    • setUnknownFields

      public final RedisProxy.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      setUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      setUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>

    • mergeUnknownFields

      public final RedisProxy.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      mergeUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.Builder>