From 800dedc14229216bab07e86aea6ea1f8c2c4c9de Mon Sep 17 00:00:00 2001 From: Dmitry Tantsur Date: Tue, 2 Feb 2016 14:42:14 +0100 Subject: [PATCH] Clean up documentation on introspection rules conditions A follow-up to commit d6ff54faf763ccf11d5799d134b176f9b4eedfcc. Change-Id: Iff1a9b342b9c34debff5465e6f27500a20809f54 --- doc/source/usage.rst | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/doc/source/usage.rst b/doc/source/usage.rst index 4e811c1bb..607e27b79 100644 --- a/doc/source/usage.rst +++ b/doc/source/usage.rst @@ -61,11 +61,15 @@ Conditions A condition is represented by an object with fields: -``op`` the type of comparison operation, default available operators include : -``eq``, ``le``, ``ge``, ``ne``, ``lt``, ``gt`` (basic comparison operators), -``in-net`` (checks that IP address is in a given network), ``contains``, -``matches`` (check field against a regular expression, matches require a full -match). +``op`` the type of comparison operation, default available operators include: + +* ``eq``, ``le``, ``ge``, ``ne``, ``lt``, ``gt`` - basic comparison operators; + +* ``in-net`` - checks that an IP address is in a given network; + +* ``matches`` - requires a full match against a given regular expression; + +* ``contains`` - requires a value to contain a given regular expression. ``field`` a `JSON path `_ to the field in the introspection data to use in comparison.