What backwards incompatibility it may introduce.
The change has been tested on both Rocky 8 and Rocky 9 aquilon hosts with filebeat. This change allows filebeat to work on Rocky 9 while not showing negative effects for existing Rocky 8 hosts.
Services which configures filebeat.yml using this module should ensure that it continues to produce the correct configuration.
Why the change is necessary. To append the schema to support configuration
seccomp
default action. This is because in Rocky 9 filebeat may be presented to start See: https://www.elastic.co/guide/en/beats/filebeat/6.8/linux-seccomp.html)resolves #1699
What backwards incompatibility it may introduce. The change has been tested on both Rocky 8 and Rocky 9 aquilon hosts with filebeat. This change allows filebeat to work on Rocky 9 while not showing negative effects for existing Rocky 8 hosts. Services which configures filebeat.yml using this module should ensure that it continues to produce the correct configuration.