Project

General

Profile

Actions

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 over 10 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Category:
-
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

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.


Subtasks 2 (0 open2 closed)

User story #5335: Set the value of the system variable RUDDER_REPORT_MODEReleasedFrançois ARMAND2014-09-05Actions
Bug #5494: Compilation error: missing modification in the PRReleasedFrançois ARMAND2014-09-05Actions
Actions #1

Updated by François ARMAND over 10 years ago

  • 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
Actions #2

Updated by François ARMAND over 10 years ago

  • 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)
Actions #3

Updated by François ARMAND over 10 years ago

  • Project changed from 34 to Rudder
  • Parent task deleted (#5293)
Actions #4

Updated by François ARMAND over 10 years ago

  • Parent task set to #5293
Actions #5

Updated by François ARMAND over 10 years ago

  • 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.

Actions #6

Updated by François ARMAND over 10 years ago

  • 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
Actions #7

Updated by François ARMAND about 10 years ago

  • Status changed from 10 to Pending release
  • % Done changed from 0 to 100
Actions #9

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 140 to 3.0.0~beta1
Actions #10

Updated by Vincent MEMBRÉ almost 10 years ago

  • 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.

Actions #11

Updated by Benoît PECCATTE over 9 years ago

  • Tracker changed from Enhancement to User story
Actions

Also available in: Atom PDF