Interface ConfigDumpOrBuilder

All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
All Known Implementing Classes:
ConfigDump, ConfigDump.Builder

public interface ConfigDumpOrBuilder extends com.google.protobuf.MessageOrBuilder
  • Method Summary

    Modifier and Type
    Method
    Description
    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.
    int
    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>
    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.

    Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder

    isInitialized

    Methods inherited from interface com.google.protobuf.MessageOrBuilder

    findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
  • Method Details

    • getConfigsList

      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;
    • getConfigs

      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;
    • getConfigsCount

      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;
    • getConfigsOrBuilderList

      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;
    • getConfigsOrBuilder

      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;