Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Compare: Overview

Showing with 1 addition and 1 deletion.
  1. +1 −1  Overview.md
View
2  Overview.md
@@ -121,7 +121,7 @@ You can think about action rules as about the most concrete ones - as they don't
(Almost) Every action uses rules to alter its' behavior. For example *notify.email* action uses rule *to* in order to determine where should email be sent to. Just like with execution context, the requested rule can be described by more than one token. For example, `:sendmail,:command`. When rule is requested, following things happen (let's imagine that *notify.email* from the previous example requested `:sendmail,:command` rule's contents):
1. Rule's context is appended to current execution context. Rule's context is `:sendmail,:command`. Execution context is: `:some_conf,:check,:onfail,:continue,:notify,:email`. So total (or *absolute*) context is: `:some_conf,:check,:onfail,:continue,:notify,:email,:sendmail,:command`.
-2. *Absolute context* is matched against every rule that was previously defined. The order of matching is: from newest rules to oldest ones (in respect to the time when they were declared). If the match is found, the rule is executed and result is returned. If the match is not found, result is returned.
+1. *Absolute context* is matched against every rule that was previously defined. The order of matching is: from newest rules to oldest ones (in respect to the time when they were declared). If the match is found, the rule is executed and result is returned. If the match is not found, result is returned.
Here's the algorithm of matching execution context against a rule:
* If the rule doesn't contain `:*` then it matches only when it is equal to execution context.
Something went wrong with that request. Please try again.