User story #7221
closed
User story #1808: Add an Audit mode to Rudder: only check properties, no modification on nodes
Set dry-run mode on each directive call
Added by Benoît PECCATTE about 9 years ago.
Updated about 8 years ago.
Category:
Web - Config management
Description
The dry-run mode is set via set_dry_run_mode and unset_dry_run_mode.
There should be a call to these bundles prior to each call to a directive bundle.
This is done in the string template variable RUDDER_DIRECTIVES_SEQUENCE
Note that promiser to those calls must be unique.
- Target version changed from 3.2.0~beta1 to 3.2.0~rc1
- Target version changed from 3.2.0~rc1 to 3.2.0~rc2
- Target version changed from 3.2.0~rc2 to 3.2.0
- Target version changed from 3.2.0 to 4.0.0~rc2
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1193
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Related to User story #9227: Generation must fail if a node has non compatible audit/enforce mode on multi-instance technique added
- Related to deleted (User story #9227: Generation must fail if a node has non compatible audit/enforce mode on multi-instance technique)
- Related to Bug #9303: Policy Mode is not used to know if a node configuration changed added
- Target version changed from 4.0.0~rc2 to 318
- Target version changed from 318 to 4.0.0~rc2
- Target version changed from 4.0.0~rc2 to 4.0.0~rc1
- Related to deleted (Bug #9303: Policy Mode is not used to know if a node configuration changed)
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Jonathan CLARKE 
Updated by 
Updated by