Bug #14954
closed
Stop auditing the default field in settings
Description
This field cannot be set by the user, and not every change to this field changes the behavior of the system.
Updated by Dominic Cleal over 8 years ago
- Related to Bug #13574: Plugins with Setting subclasses raise super: no superclass method `load_defaults' error added
Updated by Dominic Cleal over 8 years ago
- Category set to Settings
- Status changed from New to Assigned
If some updates to the default value change the behaviour, then that seems reason enough to audit it.
Updated by Shimon Shtein over 8 years ago
I have a case (downstream theme) where a plugin wants to change the default. This causes ping-pong updates with foreman core each system start and everything since it's audited, I have two audit messages for each setting.
Updated by Anonymous
Updated by Iain Walmsley almost 7 years ago
I can confirm this is still an issue in 1.15.2, this proves to create an excessive amount of spam in the audits when there are multiple Foreman in a cluster which swamps the useful auditing that takes place.
Updated by Thomas BAERT about 6 years ago
Hello,
The problem is still present in 1.18.0.
Updated by yifat makias over 3 years ago
- Status changed from Assigned to Rejected
This is not relevant anymore because the default will be dropped in newer versions.