mark sets lightweight metadata marks on the request Context. Marks may be boolean (presence) or string values and can be read by downstream plugins for routing or policy decisions.
name (required): mark keyvalue (optional): string value to set; if omitted the mark is boolean true.Exec string format: "mark key [value]".
Examples:
plugins:
- exec: mark:vip_customer
- exec: mark:priority high
bool metadata and value marks as String metadata under the provided key.mark to annotate requests for conditional plugin logic (e.g., bypass cache, prefer upstreams, or tag telemetry).