// Module included in the following assemblies:
//
// * security/file_integrity_operator/file-integrity-operator-release-notes.adoc

:_mod-docs-content-type: REFERENCE
[id="file-integrity-operator-release-notes-0-1-24_{context}"]
= Release notes for OpenShift File Integrity Operator 0.1.24

[role="_abstract"]
Release notes for OpenShift File Integrity Operator 0.1.24.


The following Red Hat Bug Fix Advisory (RHBA) is available for the OpenShift File Integrity Operator 0.1.24:

* link:https://access.redhat.com/errata/RHBA-2022:1331[RHBA-2022:1331 OpenShift File Integrity Operator Bug Fix]

[id="file-integrity-operator-0-1-24-new-features-and-enhancements_{context}"]
== New features and enhancements

* You can now configure the maximum number of backups stored in the `FileIntegrity` Custom Resource (CR) with the `config.maxBackups` attribute. This attribute specifies the number of AIDE database and log backups left over from the `re-init` process to keep on the node. Older backups beyond the configured number are automatically pruned. The default is set to five backups.

[id="openshift-file-integrity-operator-0-1-24-bug-fixes_{context}"]
== Bug fixes

* Before this update, upgrading the Operator from versions older than 0.1.21 to 0.1.22 could cause the `re-init` feature to fail. This was a result of the Operator failing to update `configMap` resource labels. Now, upgrading to the latest version fixes the resource labels. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2049206[*BZ#2049206*])

* Before this update, when enforcing the default `configMap` script contents, the wrong data keys were compared. This resulted in the `aide-reinit` script not being updated properly after an Operator upgrade, and caused the `re-init` process to fail. Now,`daemonSets` run to completion and the AIDE database `re-init` process executes successfully. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2072058[*BZ#2072058*])

