audited_changes column is too small
|Assigned To:||Amir Fefer|
|Found in release:||Pull request:||https://github.com/theforeman/foreman/pull/4556|
|Velocity based estimate||-|
I had an issue this morning when updating a quite long param in foreman:
Data too long for column 'audited_changes' at row 1
A simple fix to this problem was to hack into foreman DB and run "ALTER TABLE audits MODIFY audited_changes MEDIUMTEXT;"
#2 Updated by Joe Mader about 1 year ago
I've run into this same scenario. We don't use a "sideband" CM platform for tracking host metadata and thus some of our host-specific parameter values stored in the Foreman DB are rather large.
I was not able to conveniently locate an "admin-facing" tunable which could either turn auditing off or otherwise "filter" what gets audited.
Coincidentally, we resorted to changing the "audited_changes" column type to MEDIUMTEXT as a testing workaround. My concern is that this approach is not quite "future proof" (easily superceded by an upstream rails DB migration). Are there notable objections to making MEDIUMTEXT the new default? Given that there appears to be no fulltext index on this column, Foreman system owners would just need to ensure sufficient filesystem storage.