Class MethodMatch.ParameterMatchSpecifier.Builder

    • Method Detail

      • getDescriptor

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

        protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
        Specified by:
        internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<MethodMatch.ParameterMatchSpecifier.Builder>
      • getDescriptorForType

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

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

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

        public MethodMatch.ParameterMatchSpecifier buildPartial()
        Specified by:
        buildPartial in interface com.google.protobuf.Message.Builder
        Specified by:
        buildPartial in interface com.google.protobuf.MessageLite.Builder
      • isInitialized

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

        public boolean hasExactMatch()
         If specified, header match will be performed based on the value of the header.
         
        string exact_match = 3;
        Specified by:
        hasExactMatch in interface MethodMatch.ParameterMatchSpecifierOrBuilder
        Returns:
        Whether the exactMatch field is set.
      • getExactMatchBytes

        public com.google.protobuf.ByteString getExactMatchBytes()
         If specified, header match will be performed based on the value of the header.
         
        string exact_match = 3;
        Specified by:
        getExactMatchBytes in interface MethodMatch.ParameterMatchSpecifierOrBuilder
        Returns:
        The bytes for exactMatch.
      • setExactMatch

        public MethodMatch.ParameterMatchSpecifier.Builder setExactMatch​(String value)
         If specified, header match will be performed based on the value of the header.
         
        string exact_match = 3;
        Parameters:
        value - The exactMatch to set.
        Returns:
        This builder for chaining.
      • clearExactMatch

        public MethodMatch.ParameterMatchSpecifier.Builder clearExactMatch()
         If specified, header match will be performed based on the value of the header.
         
        string exact_match = 3;
        Returns:
        This builder for chaining.
      • setExactMatchBytes

        public MethodMatch.ParameterMatchSpecifier.Builder setExactMatchBytes​(com.google.protobuf.ByteString value)
         If specified, header match will be performed based on the value of the header.
         
        string exact_match = 3;
        Parameters:
        value - The bytes for exactMatch to set.
        Returns:
        This builder for chaining.
      • hasRangeMatch

        public boolean hasRangeMatch()
         If specified, header match will be performed based on range.
         The rule will match if the request header value is within this range.
         The entire request header value must represent an integer in base 10 notation: consisting
         of an optional plus or minus sign followed by a sequence of digits. The rule will not match
         if the header value does not represent an integer. Match will fail for empty values,
         floating point numbers or if only a subsequence of the header value is an integer.
         Examples:
         * For range [-10,0), route will match for header value -1, but not for 0,
           "somestring", 10.9, "-1somestring"
         
        .envoy.type.Int64Range range_match = 4;
        Specified by:
        hasRangeMatch in interface MethodMatch.ParameterMatchSpecifierOrBuilder
        Returns:
        Whether the rangeMatch field is set.
      • getRangeMatch

        public Int64Range getRangeMatch()
         If specified, header match will be performed based on range.
         The rule will match if the request header value is within this range.
         The entire request header value must represent an integer in base 10 notation: consisting
         of an optional plus or minus sign followed by a sequence of digits. The rule will not match
         if the header value does not represent an integer. Match will fail for empty values,
         floating point numbers or if only a subsequence of the header value is an integer.
         Examples:
         * For range [-10,0), route will match for header value -1, but not for 0,
           "somestring", 10.9, "-1somestring"
         
        .envoy.type.Int64Range range_match = 4;
        Specified by:
        getRangeMatch in interface MethodMatch.ParameterMatchSpecifierOrBuilder
        Returns:
        The rangeMatch.
      • setRangeMatch

        public MethodMatch.ParameterMatchSpecifier.Builder setRangeMatch​(Int64Range value)
         If specified, header match will be performed based on range.
         The rule will match if the request header value is within this range.
         The entire request header value must represent an integer in base 10 notation: consisting
         of an optional plus or minus sign followed by a sequence of digits. The rule will not match
         if the header value does not represent an integer. Match will fail for empty values,
         floating point numbers or if only a subsequence of the header value is an integer.
         Examples:
         * For range [-10,0), route will match for header value -1, but not for 0,
           "somestring", 10.9, "-1somestring"
         
        .envoy.type.Int64Range range_match = 4;
      • setRangeMatch

        public MethodMatch.ParameterMatchSpecifier.Builder setRangeMatch​(Int64Range.Builder builderForValue)
         If specified, header match will be performed based on range.
         The rule will match if the request header value is within this range.
         The entire request header value must represent an integer in base 10 notation: consisting
         of an optional plus or minus sign followed by a sequence of digits. The rule will not match
         if the header value does not represent an integer. Match will fail for empty values,
         floating point numbers or if only a subsequence of the header value is an integer.
         Examples:
         * For range [-10,0), route will match for header value -1, but not for 0,
           "somestring", 10.9, "-1somestring"
         
        .envoy.type.Int64Range range_match = 4;
      • mergeRangeMatch

        public MethodMatch.ParameterMatchSpecifier.Builder mergeRangeMatch​(Int64Range value)
         If specified, header match will be performed based on range.
         The rule will match if the request header value is within this range.
         The entire request header value must represent an integer in base 10 notation: consisting
         of an optional plus or minus sign followed by a sequence of digits. The rule will not match
         if the header value does not represent an integer. Match will fail for empty values,
         floating point numbers or if only a subsequence of the header value is an integer.
         Examples:
         * For range [-10,0), route will match for header value -1, but not for 0,
           "somestring", 10.9, "-1somestring"
         
        .envoy.type.Int64Range range_match = 4;
      • clearRangeMatch

        public MethodMatch.ParameterMatchSpecifier.Builder clearRangeMatch()
         If specified, header match will be performed based on range.
         The rule will match if the request header value is within this range.
         The entire request header value must represent an integer in base 10 notation: consisting
         of an optional plus or minus sign followed by a sequence of digits. The rule will not match
         if the header value does not represent an integer. Match will fail for empty values,
         floating point numbers or if only a subsequence of the header value is an integer.
         Examples:
         * For range [-10,0), route will match for header value -1, but not for 0,
           "somestring", 10.9, "-1somestring"
         
        .envoy.type.Int64Range range_match = 4;
      • getRangeMatchBuilder

        public Int64Range.Builder getRangeMatchBuilder()
         If specified, header match will be performed based on range.
         The rule will match if the request header value is within this range.
         The entire request header value must represent an integer in base 10 notation: consisting
         of an optional plus or minus sign followed by a sequence of digits. The rule will not match
         if the header value does not represent an integer. Match will fail for empty values,
         floating point numbers or if only a subsequence of the header value is an integer.
         Examples:
         * For range [-10,0), route will match for header value -1, but not for 0,
           "somestring", 10.9, "-1somestring"
         
        .envoy.type.Int64Range range_match = 4;
      • getRangeMatchOrBuilder

        public Int64RangeOrBuilder getRangeMatchOrBuilder()
         If specified, header match will be performed based on range.
         The rule will match if the request header value is within this range.
         The entire request header value must represent an integer in base 10 notation: consisting
         of an optional plus or minus sign followed by a sequence of digits. The rule will not match
         if the header value does not represent an integer. Match will fail for empty values,
         floating point numbers or if only a subsequence of the header value is an integer.
         Examples:
         * For range [-10,0), route will match for header value -1, but not for 0,
           "somestring", 10.9, "-1somestring"
         
        .envoy.type.Int64Range range_match = 4;
        Specified by:
        getRangeMatchOrBuilder in interface MethodMatch.ParameterMatchSpecifierOrBuilder