Map of attribute names to StringMatch type. Each map element specifies one condition to match.

Example:

clause: source.uid: exact: SOURCEUID request.httpmethod: exact: POST

List of attributes that are generated when any of the HTTP patterns match. This list typically includes the “api.service” and “api.version” attributes.

List of HTTP patterns to match.

List of APIKey that describes how to extract an API-KEY from an HTTP request. The first API-Key match found in the list is used, i.e. ‘OR’ semantics.

The following default policies are used to generate the request.api_key attribute if no explicit APIKey is defined.

query: key,query: api_key, and thenheader: x-api-key`

One or more services to map the listed HTTPAPISpec onto.

One or more HTTPAPISpec references that should be mapped to the specified service(s). The aggregate collection of match conditions defined in the HTTPAPISpecs should not overlap.

List of attributes that are generated if the HTTP request matches the specified httpmethod and uritemplate. This typically includes the “api.operation” attribute.

HTTP request method to match against as defined by . For example: GET, HEAD, POST, PUT, DELETE.

URI template to match against as defined by rfc6570. For example, the following are valid URI templates:

/pets
/pets/{id}
/dictionary/{term:1}/{term}
/search{?q,lang}

EXPERIMENTAL:

ecmascript style regex-based match as defined by . For example,

“^/pets/(.?)?”

The short name of the HTTPAPISpec. This is the resource name defined by the metadata name field.

Optional namespace of the HTTPAPISpec. Defaults to the encompassing HTTPAPISpecBinding’s metadata namespace field.

The short name of the service such as “foo”.

Optional namespace of the service. Defaults to value of metadata namespace field.

Domain suffix used to construct the service FQDN in implementations that support such specification.

The service FQDN.

Optional one or more labels that uniquely identify the service version.

Note: When used for a VirtualService destination, labels MUST be empty.

Specifies the behavior when the client is unable to connect to Mixer.

Max retries on transport error.

Base time to wait between retries. Will be adjusted by exponential backoff and jitter.

Max time to wait between retries.

If network connection fails, request is allowed and delivered to the service.

If network connection fails, request is rejected.

The quota name to charge

The quota amount to charge

If empty, match all request. If any of match is true, it is matched.

The list of quotas to charge.

One or more services to map the listed QuotaSpec onto.

One or more QuotaSpec references that should be mapped to the specified service(s). The aggregate collection of match conditions defined in the QuotaSpecs should not overlap.

The short name of the QuotaSpec. This is the resource name defined by the metadata name field.

Optional namespace of the QuotaSpec. Defaults to the value of the metadata namespace field.

If true, do not call Mixer Check.

If true, do not call Mixer Report.

Send these attributes to Mixer in both Check and Report. This typically includes the “destination.service” attribute. In case of a per-route override, per-route attributes take precedence over the attributes supplied in the client configuration.

HTTP API specifications to generate API attributes.

Specifies the behavior when the client is unable to connect to Mixer. This is the service-level policy. It overrides [mesh-level policy][istio.mixer.v1.config.client.TransportConfig.networkfailpolicy].

Default attributes to forward to upstream. This typically includes the “source.ip” and “source.uid” attributes. In case of a per-route override, per-route attributes take precedence over the attributes supplied in the client configuration.

Forwarded attributes take precedence over the static Mixer attributes, except in cases where there is clear configuration to ignore forwarded attributes. Gateways, for instance, should never use forwarded attributes.

The full order of application is as follows: 1. static Mixer attributes from the filter config; 2. static Mixer attributes from the route config; 3. forwarded attributes from the source filter config (if any and not ignored); 4. forwarded attributes from the source route config (if any and not ignored); 5. derived attributes from the request metadata.

exact string match

prefix-based match

ECMAscript style regex-based match

The transport config.

Default attributes to send to Mixer in both Check and Report. This typically includes “destination.ip” and “destination.uid” attributes.

If set to true, disables Mixer check calls.

If set to true, disables Mixer check calls.

Quota specifications to generate quota requirements. It applies on the new TCP connections.

Specify report interval to send periodical reports for long TCP connections. If not specified, the interval is 10 seconds. This interval should not be less than 1 second, otherwise it will be reset to 1 second.

A map of attribute name to its value.