Class ConfigDump.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<ConfigDump.Builder>
com.google.protobuf.GeneratedMessage.Builder<ConfigDump.Builder>
io.envoyproxy.envoy.admin.v3.ConfigDump.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, ConfigDumpOrBuilder, Cloneable
Enclosing class:
ConfigDump

public static final class ConfigDump.Builder extends com.google.protobuf.GeneratedMessage.Builder<ConfigDump.Builder> implements ConfigDumpOrBuilder
 The :ref:`/config_dump <operations_admin_interface_config_dump>` admin endpoint uses this wrapper
 message to maintain and serve arbitrary configuration information from any component in Envoy.
 
Protobuf type envoy.admin.v3.ConfigDump
  • Field Summary

    Fields
    Modifier and Type
    Field
    Description
    private int
     
    private List<com.google.protobuf.Any>
     
    private com.google.protobuf.RepeatedFieldBuilder<com.google.protobuf.Any,com.google.protobuf.Any.Builder,com.google.protobuf.AnyOrBuilder>
     
  • Constructor Summary

    Constructors
    Modifier
    Constructor
    Description
    private
     
    private
    Builder(com.google.protobuf.AbstractMessage.BuilderParent parent)
     
  • Method Summary

    Modifier and Type
    Method
    Description
    addAllConfigs(Iterable<? extends com.google.protobuf.Any> values)
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    addConfigs(int index, com.google.protobuf.Any value)
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    addConfigs(int index, com.google.protobuf.Any.Builder builderForValue)
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    addConfigs(com.google.protobuf.Any value)
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    addConfigs(com.google.protobuf.Any.Builder builderForValue)
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    com.google.protobuf.Any.Builder
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    com.google.protobuf.Any.Builder
    addConfigsBuilder(int index)
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
     
     
    private void
     
    private void
     
     
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    private void
     
    com.google.protobuf.Any
    getConfigs(int index)
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    com.google.protobuf.Any.Builder
    getConfigsBuilder(int index)
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    List<com.google.protobuf.Any.Builder>
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    int
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    private com.google.protobuf.RepeatedFieldBuilder<com.google.protobuf.Any,com.google.protobuf.Any.Builder,com.google.protobuf.AnyOrBuilder>
     
    List<com.google.protobuf.Any>
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    com.google.protobuf.AnyOrBuilder
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    List<? extends com.google.protobuf.AnyOrBuilder>
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
     
    static final com.google.protobuf.Descriptors.Descriptor
     
    com.google.protobuf.Descriptors.Descriptor
     
    protected com.google.protobuf.GeneratedMessage.FieldAccessorTable
     
    final boolean
     
    mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry)
     
    mergeFrom(com.google.protobuf.Message other)
     
     
    removeConfigs(int index)
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    setConfigs(int index, com.google.protobuf.Any value)
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
    setConfigs(int index, com.google.protobuf.Any.Builder builderForValue)
    This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.

    Methods inherited from class com.google.protobuf.GeneratedMessage.Builder

    addRepeatedField, clearField, clearOneof, clone, getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMapFieldReflection, internalGetMutableMapField, internalGetMutableMapFieldReflection, isClean, markClean, mergeUnknownFields, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setField, setRepeatedField, setUnknownFields, setUnknownFieldSetBuilder, setUnknownFieldsProto3

    Methods inherited from class com.google.protobuf.AbstractMessage.Builder

    findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toString

    Methods inherited from class com.google.protobuf.AbstractMessageLite.Builder

    addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageException

    Methods inherited from class java.lang.Object

    equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

    Methods inherited from interface com.google.protobuf.Message.Builder

    mergeDelimitedFrom, mergeDelimitedFrom

    Methods inherited from interface com.google.protobuf.MessageLite.Builder

    mergeFrom

    Methods inherited from interface com.google.protobuf.MessageOrBuilder

    findInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
  • Field Details

    • bitField0_

      private int bitField0_
    • configs_

      private List<com.google.protobuf.Any> configs_
    • configsBuilder_

      private com.google.protobuf.RepeatedFieldBuilder<com.google.protobuf.Any,com.google.protobuf.Any.Builder,com.google.protobuf.AnyOrBuilder> configsBuilder_
  • Constructor Details

    • Builder

      private Builder()
    • Builder

      private Builder(com.google.protobuf.AbstractMessage.BuilderParent parent)
  • Method Details

    • getDescriptor

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

      protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessage.Builder<ConfigDump.Builder>
    • clear

      public ConfigDump.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.GeneratedMessage.Builder<ConfigDump.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.GeneratedMessage.Builder<ConfigDump.Builder>
    • getDefaultInstanceForType

      public ConfigDump getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder
    • build

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

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

      private void buildPartialRepeatedFields(ConfigDump result)
    • buildPartial0

      private void buildPartial0(ConfigDump result)
    • mergeFrom

      public ConfigDump.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<ConfigDump.Builder>
    • mergeFrom

      public ConfigDump.Builder mergeFrom(ConfigDump other)
    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessage.Builder<ConfigDump.Builder>
    • mergeFrom

      public ConfigDump.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<ConfigDump.Builder>
      Throws:
      IOException
    • ensureConfigsIsMutable

      private void ensureConfigsIsMutable()
    • getConfigsList

      public List<com.google.protobuf.Any> getConfigsList()
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
      Specified by:
      getConfigsList in interface ConfigDumpOrBuilder
    • getConfigsCount

      public int getConfigsCount()
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
      Specified by:
      getConfigsCount in interface ConfigDumpOrBuilder
    • getConfigs

      public com.google.protobuf.Any getConfigs(int index)
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
      Specified by:
      getConfigs in interface ConfigDumpOrBuilder
    • setConfigs

      public ConfigDump.Builder setConfigs(int index, com.google.protobuf.Any value)
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • setConfigs

      public ConfigDump.Builder setConfigs(int index, com.google.protobuf.Any.Builder builderForValue)
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • addConfigs

      public ConfigDump.Builder addConfigs(com.google.protobuf.Any value)
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • addConfigs

      public ConfigDump.Builder addConfigs(int index, com.google.protobuf.Any value)
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • addConfigs

      public ConfigDump.Builder addConfigs(com.google.protobuf.Any.Builder builderForValue)
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • addConfigs

      public ConfigDump.Builder addConfigs(int index, com.google.protobuf.Any.Builder builderForValue)
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • addAllConfigs

      public ConfigDump.Builder addAllConfigs(Iterable<? extends com.google.protobuf.Any> values)
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • clearConfigs

      public ConfigDump.Builder clearConfigs()
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • removeConfigs

      public ConfigDump.Builder removeConfigs(int index)
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • getConfigsBuilder

      public com.google.protobuf.Any.Builder getConfigsBuilder(int index)
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • getConfigsOrBuilder

      public com.google.protobuf.AnyOrBuilder getConfigsOrBuilder(int index)
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
      Specified by:
      getConfigsOrBuilder in interface ConfigDumpOrBuilder
    • getConfigsOrBuilderList

      public List<? extends com.google.protobuf.AnyOrBuilder> getConfigsOrBuilderList()
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
      Specified by:
      getConfigsOrBuilderList in interface ConfigDumpOrBuilder
    • addConfigsBuilder

      public com.google.protobuf.Any.Builder addConfigsBuilder()
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • addConfigsBuilder

      public com.google.protobuf.Any.Builder addConfigsBuilder(int index)
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • getConfigsBuilderList

      public List<com.google.protobuf.Any.Builder> getConfigsBuilderList()
       This list is serialized and dumped in its entirety at the
       :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.
      
       The following configurations are currently supported and will be dumped in the order given
       below:
      
       * ``bootstrap``: :ref:`BootstrapConfigDump <envoy_v3_api_msg_admin.v3.BootstrapConfigDump>`
       * ``clusters``: :ref:`ClustersConfigDump <envoy_v3_api_msg_admin.v3.ClustersConfigDump>`
       * ``ecds_filter_http``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_quic_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``ecds_filter_tcp_listener``: :ref:`EcdsConfigDump <envoy_v3_api_msg_admin.v3.EcdsConfigDump>`
       * ``endpoints``:  :ref:`EndpointsConfigDump <envoy_v3_api_msg_admin.v3.EndpointsConfigDump>`
       * ``listeners``: :ref:`ListenersConfigDump <envoy_v3_api_msg_admin.v3.ListenersConfigDump>`
       * ``scoped_routes``: :ref:`ScopedRoutesConfigDump <envoy_v3_api_msg_admin.v3.ScopedRoutesConfigDump>`
       * ``routes``:  :ref:`RoutesConfigDump <envoy_v3_api_msg_admin.v3.RoutesConfigDump>`
       * ``secrets``:  :ref:`SecretsConfigDump <envoy_v3_api_msg_admin.v3.SecretsConfigDump>`
      
       EDS Configuration will only be dumped by using parameter ``?include_eds``
      
       Currently ECDS is supported in HTTP and listener filters. Note, ECDS configuration for
       either HTTP or listener filter will only be dumped if it is actually configured.
      
       You can filter output with the resource and mask query parameters.
       See :ref:`/config_dump?resource={} <operations_admin_interface_config_dump_by_resource>`,
       :ref:`/config_dump?mask={} <operations_admin_interface_config_dump_by_mask>`,
       or :ref:`/config_dump?resource={},mask={}
       <operations_admin_interface_config_dump_by_resource_and_mask>` for more information.
       
      repeated .google.protobuf.Any configs = 1;
    • getConfigsFieldBuilder

      private com.google.protobuf.RepeatedFieldBuilder<com.google.protobuf.Any,com.google.protobuf.Any.Builder,com.google.protobuf.AnyOrBuilder> getConfigsFieldBuilder()