Struct TrafficLabelPlugin 

pub struct TrafficLabelPlugin {
    rules: Vec<Rule>,
}

Applies the first matching rule’s action: header values and label values are $var templates interpolated per request.

Fields

rules: Vec<Rule>

Implementations

impl TrafficLabelPlugin

pub fn from_config(config: &HashMap<String, Value>) -> Result<Self, String>

Builds the plugin from node config. All expressions are validated here at config load.

Accepted keys:

• rules (array, required, non-empty): evaluated in order; the first rule whose match passes applies one of its actions.
  • match (array, optional): APISIX triple-array condition, rules AND-ed. Omit to match every request.
  • actions (array of objects, required, non-empty): one entry is chosen by weighted round-robin. Each entry:
    • set_headers (object {name: value}): request headers to set (replacing existing values); values support $var interpolation.
    • set_labels (object {key: value}, featherbit extension): written to context.message as label.<key>; values support $var interpolation.
    • weight (integer >= 1, default 1): selection weight.

type: traffic-label
config:
  rules:
    - match:
        - ["arg_channel", "==", "beta"]
      actions:
        - set_headers:
            x-server-id: beta
          set_labels:
            tier: "beta"
          weight: 3
        - set_headers:
            x-server-id: stable
          weight: 1

Trait Implementations

impl Plugin for TrafficLabelPlugin

fn plugin_type(&self) -> &str

Unique identifier for the plugin type (e.g., “proxy-rewrite”, “upstream”).

fn execute<'life0, 'life1, 'async_trait>( &'life0 self, ctx: Context, _named_inputs: &'life1 HashMap<String, Value>, ) -> Pin<Box<dyn Future<Output = Result<PluginOutput, PluginExecutionError>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait,

Executes the plugin logic against the request/response context.