shared_rule
defines a re-usable mapping of traffic between clusters and routes. This can be very simple, or very complex, depending on the need and the stage of deployment. In its most simple setup, any given request is just sent to a single cluster. However, traffic can also be fractionally diverted and/or simultaneously shadowed to alternate clusters.NOTE Some features of theshared_rules
object can also be defined in the route object. When defined inline, they cannot be shared between proxies.
shared_rules_key
name
"shared_rules_key"
on all routes linked to this shared rule.zone_key
default
default
field defines cluster_constraint arrays that map requests to clusters. Currently, the only implemented field is the light
field which is used to determine the Instance to which the live request will be sent and from which the response will be sent to the caller.NOTE:default
also contains adark
and alight
field which currently have no effect.dark
array will be used in future versions to support traffic shadowing to Instances. Similarly thetap
array will determine an Instance to send a copy of the request to, comparing the response to thelight
response.
rules
response_data
cohort_seed
properties
retry_policy
checksum