Package io.envoyproxy.envoy.admin.v3
Class ConfigDump.Builder
- java.lang.Object
-
- com.google.protobuf.AbstractMessageLite.Builder
-
- com.google.protobuf.AbstractMessage.Builder<BuilderT>
-
- 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,java.lang.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 typeenvoy.admin.v3.ConfigDump
-
-
Field Summary
Fields Modifier and Type Field Description private intbitField0_private java.util.List<com.google.protobuf.Any>configs_private com.google.protobuf.RepeatedFieldBuilder<com.google.protobuf.Any,com.google.protobuf.Any.Builder,com.google.protobuf.AnyOrBuilder>configsBuilder_
-
Method Summary
All Methods Static Methods Instance Methods Concrete Methods Modifier and Type Method Description ConfigDump.BuilderaddAllConfigs(java.lang.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.ConfigDump.BuilderaddConfigs(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.ConfigDump.BuilderaddConfigs(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.ConfigDump.BuilderaddConfigs(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.ConfigDump.BuilderaddConfigs(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.BuilderaddConfigsBuilder()This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.com.google.protobuf.Any.BuilderaddConfigsBuilder(int index)This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.ConfigDumpbuild()ConfigDumpbuildPartial()private voidbuildPartial0(ConfigDump result)private voidbuildPartialRepeatedFields(ConfigDump result)ConfigDump.Builderclear()ConfigDump.BuilderclearConfigs()This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.private voidensureConfigsIsMutable()com.google.protobuf.AnygetConfigs(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.BuildergetConfigsBuilder(int index)This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.java.util.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.intgetConfigsCount()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>getConfigsFieldBuilder()java.util.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.com.google.protobuf.AnyOrBuildergetConfigsOrBuilder(int index)This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.java.util.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.ConfigDumpgetDefaultInstanceForType()static com.google.protobuf.Descriptors.DescriptorgetDescriptor()com.google.protobuf.Descriptors.DescriptorgetDescriptorForType()protected com.google.protobuf.GeneratedMessage.FieldAccessorTableinternalGetFieldAccessorTable()booleanisInitialized()ConfigDump.BuildermergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry)ConfigDump.BuildermergeFrom(com.google.protobuf.Message other)ConfigDump.BuildermergeFrom(ConfigDump other)ConfigDump.BuilderremoveConfigs(int index)This list is serialized and dumped in its entirety at the :ref:`/config_dump <operations_admin_interface_config_dump>` endpoint.ConfigDump.BuildersetConfigs(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.ConfigDump.BuildersetConfigs(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
-
-
-
-
Method Detail
-
getDescriptor
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
-
internalGetFieldAccessorTable
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
- Specified by:
internalGetFieldAccessorTablein classcom.google.protobuf.GeneratedMessage.Builder<ConfigDump.Builder>
-
clear
public ConfigDump.Builder clear()
- Specified by:
clearin interfacecom.google.protobuf.Message.Builder- Specified by:
clearin interfacecom.google.protobuf.MessageLite.Builder- Overrides:
clearin classcom.google.protobuf.GeneratedMessage.Builder<ConfigDump.Builder>
-
getDescriptorForType
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
- Specified by:
getDescriptorForTypein interfacecom.google.protobuf.Message.Builder- Specified by:
getDescriptorForTypein interfacecom.google.protobuf.MessageOrBuilder- Overrides:
getDescriptorForTypein classcom.google.protobuf.GeneratedMessage.Builder<ConfigDump.Builder>
-
getDefaultInstanceForType
public ConfigDump getDefaultInstanceForType()
- Specified by:
getDefaultInstanceForTypein interfacecom.google.protobuf.MessageLiteOrBuilder- Specified by:
getDefaultInstanceForTypein interfacecom.google.protobuf.MessageOrBuilder
-
build
public ConfigDump build()
- Specified by:
buildin interfacecom.google.protobuf.Message.Builder- Specified by:
buildin interfacecom.google.protobuf.MessageLite.Builder
-
buildPartial
public ConfigDump buildPartial()
- Specified by:
buildPartialin interfacecom.google.protobuf.Message.Builder- Specified by:
buildPartialin interfacecom.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:
mergeFromin interfacecom.google.protobuf.Message.Builder- Overrides:
mergeFromin classcom.google.protobuf.AbstractMessage.Builder<ConfigDump.Builder>
-
mergeFrom
public ConfigDump.Builder mergeFrom(ConfigDump other)
-
isInitialized
public final boolean isInitialized()
- Specified by:
isInitializedin interfacecom.google.protobuf.MessageLiteOrBuilder- Overrides:
isInitializedin classcom.google.protobuf.GeneratedMessage.Builder<ConfigDump.Builder>
-
mergeFrom
public ConfigDump.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws java.io.IOException
- Specified by:
mergeFromin interfacecom.google.protobuf.Message.Builder- Specified by:
mergeFromin interfacecom.google.protobuf.MessageLite.Builder- Overrides:
mergeFromin classcom.google.protobuf.AbstractMessage.Builder<ConfigDump.Builder>- Throws:
java.io.IOException
-
ensureConfigsIsMutable
private void ensureConfigsIsMutable()
-
getConfigsList
public java.util.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:
getConfigsListin interfaceConfigDumpOrBuilder
-
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:
getConfigsCountin interfaceConfigDumpOrBuilder
-
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:
getConfigsin interfaceConfigDumpOrBuilder
-
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(java.lang.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:
getConfigsOrBuilderin interfaceConfigDumpOrBuilder
-
getConfigsOrBuilderList
public java.util.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:
getConfigsOrBuilderListin interfaceConfigDumpOrBuilder
-
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 java.util.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()
-
-