Global queries FIM - Investigate impact on installation/upgrade - Wazuh Puppet

[c-bordon]

Description

The issue aims to investigate if the new files need special handling in the installation of the Wazuh central components with the Wazuh Puppet

With persistence

• /var/ossec/queue/indexer/wazuh-states-[index_name]-[cluster_name]

Without persistence

• /var/ossec/templates/[index_name]_states_template.json
• /var/ossec/templates/[index_name]_states_template.json
• /var/ossec/lib/libinventory_harvester.so

Tasks

• Investigate if these files need special handling in AIO installation with the Wazuh Puppet
• Investigate if these files need special handling in distributed installation with the Wazuh Puppet
• Investigate if we need to make changes for these updates in the ossec.conf Inventory harvester configuration wazuh#28217
• Make the necessary changes
• Test the installation methods

DRI

• @c-bordon

[vcerenu]

Update

The persistence of these files depends exclusively on the upgrade process performed by the RPM or DEB package with which the update is performed.
Puppet does not generate changes on files that do not require modification for the configuration of Wazuh manager, so it does not have any type of action on these files and their persistence will depend exclusively on the update process.
Regarding the changes on the ossec.conf file, it is necessary to add this configuration to the templates that make up the ossec.conf file, so it is necessary to know where these nodes should be placed and if they require any type of variable to be completed.