Actions
Bug #5658
closedUser story #5293: Add a 'changes only' compliance mode, only reporting changes on systems
User story #5296: Create the logic to get execution reports for "error only" mode
full-compliance default value is wrong
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Maintenance
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
compliance mode default value is wrong.
default value is "fullCompliance", but accepted values are "full-compliance" and "error-only" It works fine since we fall back to full-compliance but there is an error message
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from New to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/642
Updated by François ARMAND about 10 years ago
Ah. that's that to do convergente state, we are missing when the starting point is not OK...
Thanks !
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 3c68a15bf59b3cfb33dc6aa0e68f5861686b5c4b.
Updated by François ARMAND about 10 years ago
Applied in changeset 0b27fa7338d44639492ad7990d38752efbf6eb1d.
Updated by François ARMAND about 10 years ago
- Parent task changed from #5293 to #5296
Updated by Matthieu CERDA about 10 years ago
- Target version changed from 140 to 3.0.0~beta1
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.
- Announcement
- Changelog
- "Download information": https://www.rudder-project.org/site/get-rudder/downloads/
Actions