Project

General

Profile

Actions

Architecture #24964

closed

Remove unused tables about compliance and eventlogs

Added by François ARMAND 6 months ago. Updated 4 months ago.

Status:
Released
Priority:
N/A
Category:
Architecture - Code maintenance
Target version:
Effort required:
Name check:
To do
Fix check:
To do
Regression:
No

Description

We have these table that are all empty in a standard rudder installation:

- archivednodecompliance
- archivednodeconfigurations
- archivedruddersysevents
- nodecompliance
- migrationeventlog
- migrationeventlogid

The migration ones seems to be a leftover from when we were doing frequent migration of event logs format. The last one is from 2016.
Plus, today we wouldn't do it like it was done, with shell migration script looking for things and putting them in DB.

The 4 others need special configuration parameters to be enabled, and they are not, since is cause massive storage explosion when they are.
And since they don't provide features (appart for more storage taken), nobody enabled them.
For some, we don't even have a way to enable them at all anymore (archivedruddersysevents?). For other, they are undocumented settings (the one for API) like save_db_compliance_details

Also delete migration script, some related to 4.x migration...

EDIT: it seems that some user are actually using nodecompliance and so we will not clean it for now.


Subtasks 1 (0 open1 closed)

Architecture #25033: Do node delete table nodecomplianceReleasedClark ANDRIANASOLOActions

Related issues 2 (1 open1 closed)

Related to Rudder - Architecture #24963: Persist compliance in base to know last state for a long timePending releaseFrançois ARMANDActions
Related to Rudder - Bug #25000: Remove the outdated migration scripts from the packagingReleasedFrançois ARMANDActions
Actions

Also available in: Atom PDF