Project

General

Profile

Actions

Bug #14954

closed

Stop auditing the default field in settings

Added by Shimon Shtein almost 8 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Settings
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

This field cannot be set by the user, and not every change to this field changes the behavior of the system.


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #13574: Plugins with Setting subclasses raise super: no superclass method `load_defaults' errorClosedDominic Cleal02/05/2016Actions
Actions #1

Updated by Dominic Cleal almost 8 years ago

  • Related to Bug #13574: Plugins with Setting subclasses raise super: no superclass method `load_defaults' error added
Actions #2

Updated by Dominic Cleal almost 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.

Actions #3

Updated by Shimon Shtein almost 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.

Actions #4

Updated by Anonymous almost 7 years ago

Shimon, what's the status here?

Actions #5

Updated by Iain Walmsley about 6 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.

Actions #6

Updated by Thomas BAERT over 5 years ago

Hello,

The problem is still present in 1.18.0.

Actions #7

Updated by yifat makias almost 3 years ago

  • Status changed from Assigned to Rejected

This is not relevant anymore because the default will be dropped in newer versions.

Actions

Also available in: Atom PDF