Package io.envoyproxy.envoy.extensions.http.ext_proc.processing_request_modifiers.mapped_attribute_builder.v3

Interface MappedAttributeBuilderOrBuilder

All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
All Known Implementing Classes:
MappedAttributeBuilder, MappedAttributeBuilder.Builder
public interface MappedAttributeBuilderOrBuilder extends com.google.protobuf.MessageOrBuilder

  • Method Details

    • getMappedRequestAttributesCount

      int getMappedRequestAttributesCount()
       A map of request attributes to set in the attributes struct.
 The key is the attribute name, the value is the attribute value,
 interpretable by CEL. This allows for the re-mapping of attributes, which is not supported
 by the native attribute building logic.
      map<string, string> mapped_request_attributes = 1;

    • containsMappedRequestAttributes

      boolean containsMappedRequestAttributes(String key)
       A map of request attributes to set in the attributes struct.
 The key is the attribute name, the value is the attribute value,
 interpretable by CEL. This allows for the re-mapping of attributes, which is not supported
 by the native attribute building logic.
      map<string, string> mapped_request_attributes = 1;

    • getMappedRequestAttributes

      @Deprecated Map<String,String> getMappedRequestAttributes()
      Deprecated.
      Use getMappedRequestAttributesMap() instead.

    • getMappedRequestAttributesMap

      Map<String,String> getMappedRequestAttributesMap()
       A map of request attributes to set in the attributes struct.
 The key is the attribute name, the value is the attribute value,
 interpretable by CEL. This allows for the re-mapping of attributes, which is not supported
 by the native attribute building logic.
      map<string, string> mapped_request_attributes = 1;

    • getMappedRequestAttributesOrDefault

      String getMappedRequestAttributesOrDefault(String key, String defaultValue)
       A map of request attributes to set in the attributes struct.
 The key is the attribute name, the value is the attribute value,
 interpretable by CEL. This allows for the re-mapping of attributes, which is not supported
 by the native attribute building logic.
      map<string, string> mapped_request_attributes = 1;

    • getMappedRequestAttributesOrThrow

      String getMappedRequestAttributesOrThrow(String key)
       A map of request attributes to set in the attributes struct.
 The key is the attribute name, the value is the attribute value,
 interpretable by CEL. This allows for the re-mapping of attributes, which is not supported
 by the native attribute building logic.
      map<string, string> mapped_request_attributes = 1;

    • getMappedResponseAttributesCount

      int getMappedResponseAttributesCount()
       Similar to ``mapped_request_attributes``, but for response attributes. The
 response nomenclature here just indicates that the attributes, whatever they may be, are sent
 with a response headers, body, or trailers ext_proc call.
 If a value contains a request key, e.g., ``request.host``, then the attribute would
 just be sent along in the response. This is useful if a given ext_proc extension is only
 enabled for response handling, e.g., ``RESPONSE_HEADERS`` but the backend wants to access request
 metadata.
      map<string, string> mapped_response_attributes = 2;

    • containsMappedResponseAttributes

      boolean containsMappedResponseAttributes(String key)
       Similar to ``mapped_request_attributes``, but for response attributes. The
 response nomenclature here just indicates that the attributes, whatever they may be, are sent
 with a response headers, body, or trailers ext_proc call.
 If a value contains a request key, e.g., ``request.host``, then the attribute would
 just be sent along in the response. This is useful if a given ext_proc extension is only
 enabled for response handling, e.g., ``RESPONSE_HEADERS`` but the backend wants to access request
 metadata.
      map<string, string> mapped_response_attributes = 2;

    • getMappedResponseAttributes

      @Deprecated Map<String,String> getMappedResponseAttributes()
      Deprecated.
      Use getMappedResponseAttributesMap() instead.

    • getMappedResponseAttributesMap

      Map<String,String> getMappedResponseAttributesMap()
       Similar to ``mapped_request_attributes``, but for response attributes. The
 response nomenclature here just indicates that the attributes, whatever they may be, are sent
 with a response headers, body, or trailers ext_proc call.
 If a value contains a request key, e.g., ``request.host``, then the attribute would
 just be sent along in the response. This is useful if a given ext_proc extension is only
 enabled for response handling, e.g., ``RESPONSE_HEADERS`` but the backend wants to access request
 metadata.
      map<string, string> mapped_response_attributes = 2;

    • getMappedResponseAttributesOrDefault

      String getMappedResponseAttributesOrDefault(String key, String defaultValue)
       Similar to ``mapped_request_attributes``, but for response attributes. The
 response nomenclature here just indicates that the attributes, whatever they may be, are sent
 with a response headers, body, or trailers ext_proc call.
 If a value contains a request key, e.g., ``request.host``, then the attribute would
 just be sent along in the response. This is useful if a given ext_proc extension is only
 enabled for response handling, e.g., ``RESPONSE_HEADERS`` but the backend wants to access request
 metadata.
      map<string, string> mapped_response_attributes = 2;

    • getMappedResponseAttributesOrThrow

      String getMappedResponseAttributesOrThrow(String key)
       Similar to ``mapped_request_attributes``, but for response attributes. The
 response nomenclature here just indicates that the attributes, whatever they may be, are sent
 with a response headers, body, or trailers ext_proc call.
 If a value contains a request key, e.g., ``request.host``, then the attribute would
 just be sent along in the response. This is useful if a given ext_proc extension is only
 enabled for response handling, e.g., ``RESPONSE_HEADERS`` but the backend wants to access request
 metadata.
      map<string, string> mapped_response_attributes = 2;