User story #5294
closed
User story #5293: Add a 'changes only' compliance mode, only reporting changes on systems
Add a configuration option for the "error only" mode in admin tab
Added by François ARMAND about 10 years ago.
Updated over 9 years ago.
Description
We need some way to let the user choose in what mode Rudder works.
At first, it will be a global switch and all nodes will be in the same mode. In the future, each node could be in either compliance or error only mode.
That mode will:
- have an effect on the generated promises so that then know if they have to log success or not,
- have an effect on Rudder display to let the user knows that compliance assessment is disabled,
- have an effect on the logic that get execution reports and display them to the user/api/etc.
The parameter value will be store in LDAP.
That ticket is ONLY for the UI and storing of the parameter.
- Subject changed from Add a swith and a system variable for the "error only" mode to Add a switch and a system variable for the "error only" mode
- Subject changed from Add a switch and a system variable for the "error only" mode to Add a configuration option for the "error only" mode in admin tab
- Description updated (diff)
- Project changed from 34 to Rudder
- Parent task deleted (
#5293)
- Status changed from In progress to 10
- Pull Request set to https://github.com/Normation/rudder/pull/587https://github.com/Normation/rudder/pull/587
I did the pull request so that the code is available for other development relying on it.
- Pull Request changed from https://github.com/Normation/rudder/pull/587https://github.com/Normation/rudder/pull/587 to https://github.com/Normation/rudder/pull/587
- Status changed from 10 to Pending release
- % Done changed from 0 to 100
- Target version changed from 140 to 3.0.0~beta1
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.
- Tracker changed from Enhancement to User story
Also available in: Atom
PDF