Revision f1215697
Added by Alexis Mousset almost 7 years ago
| 22_configuration_management/40_policy_mode.txt | ||
|---|---|---|
|
* *Audit*: Test if the system is in the desired state, and report about it
|
||
|
* *Enforce*: Test if the system is in the desired state, if not, try to act to get to this state, and report about actions taken and final state
|
||
|
|
||
|
This allows for example <<_using_rudder_as_an_audit_tool, to use Rudder as an audit tool>> or <<, _using_audit_mode_to_validate_a_policy_before_applying_it, to test a policy before enforcing it>>.
|
||
|
|
||
|
image:./images/audit_mode_general_overview.png[]
|
||
|
|
||
|
This mode can be set:
|
||
|
|
||
|
* Globally on the Rudder root server. In this can case there are two options: allow to override this mode on specific items, or use the global configuration everywhere.
|
||
Also available in: Unified diff
Fixes #10667: Improve policy mode documentation