## The problem
Issue honeycombio/refinery#822 (closed, 8 comments): the Refinery rules language had no OR semantic, so testing one field against several values meant writing ugly chained regexps. Maintainers chose to add a matches operator rather than in/not-in, because in would need array values that their config YAML layer cannot handle cleanly. The matches operator shipped in PR #939.

## What fixed it
Refinery rules have no in or not-in operator, and there is no plan to add them, because the config YAML cannot cleanly take array values. For testing a field against several options, use the matches operator (added in the 2.2 line via PR #939) with a regex like ^(option1|option2|option3)$ around your values. That covers the multi-value case, and regex negation covers the not-in case too.