Architecture #24964
Updated by François ARMAND 6 months ago
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 a 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 done in DB. 2016 (o_O). 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...