...
Note: The Compliance engine can validate MCP automation outputs in addition to device configurations. To validate an automation output, select Source → Mass Config Push Result. The same condition types and matching principles described in this article apply when evaluating automation output.
Suppose the Condition type is "
...
Source contains
...
| Code Block | ||
|---|---|---|
| ||
interface Ethernet1
ip address 10.0.0.1/24 |
The table below shows the Condition evaluation status for each match mode using the example source and Condition input:
...
Match mode
...
Condition Status
...
Explanation
...
Loose
...
Successful
...
Both lines exist in the source.
...
Sequential
...
Successful
...
The lines appear in the correct order.
...
Strict
...
Failed
...
The "description Uplink" line appears between them.
condition types:
Loose Mode
Loose mode verifies that all input lines exist somewhere in the source. Their order is ignored, and any content may appear between matching lines in the source.
...
Use case | Recommended mode |
|---|---|
Verify several independent configuration lines exist in the source | Loose |
Verify the presence and order of configuration commands in the source | Sequential |
Verify an exact configuration block | Strict |
Regex matching condition types:
The same three match modes apply when using regex matching condition types. Each regex line in the input is evaluated against lines in the source, and the match mode governs whether the matches must occur in order and whether intervening unmatched lines are permitted.