Rudder

Please see the attached screenshots for the definition of the technique. the directive created from this technique is set to audit mode.

The initial contents of the file (/tmp/test) being operated on is as follows:

options     color=blue height=4 width=5

The result of the agent running is:

A| compliant     test                      File ensure key value pa| /tmp/test          Add key non existing options with value  height=4  in /tmp/test was correct
A| compliant     test                      File ensure key value pa| /tmp/test          Add key non existing options with value  width=5  in /tmp/test was correct

When the contents of the file change to:

options     color=blue height=99 width=5

the result becomes:

A| non-compliant test                      File ensure key value pa| /tmp/test          Add key non existing options with value  height=4  in /tmp/test was not correct
A| non-compliant test                      File ensure key value pa| /tmp/test          Add key non existing options with value  width=5  in /tmp/test was not correct

However, if the contents of the file are:

options     color=blue height=4 width=99

the result becomes:

A| compliant     test                      File ensure key value pa| /tmp/test          Add key non existing options with value  height=4  in /tmp/test was correct
A| non-compliant test                      File ensure key value pa| /tmp/test          Add key non existing options with value  width=5  in /tmp/test was not correct

If the order of the methods that are defined in the technique is exchanged, the behavior is the exact opposite, so it seems that whichever method is listed first, if it fails, makes the status of the second method fail even if it should be successful.