MVP - Ansible development

[YisDav]

Implementation Plan

The initial implementation plan covers the following steps in a sequential manner:

1. Ansible MVP - Cleaning of the repository and new project initial setup #1489
   • Follow the Ansible Project Structure (SPIKE - Wazuh Ansible #1461 (comment)) guidelines
   • Keep the .github/ directory
2. Ansible MVP - Workflow adaptations: Generation of pre-signed URLs for the necessary packages #1490
   • Must be able to generate pre-signed URL of each required S3 object (package) in case it isn't a Production or PreRelease package.
   • There will be three different URL list files, and will be eventually downloaded and used to generate URLs ansible variables file. Those three correspond to Development, PreRelease, and Production (qa-maintained)
   • For development packages, once each package URL has been created (based in a given, downloaded, S3 URIs list file), it must be saved and passed as a parameter for the Ansible runtime.
     • Options:
       • Ansible variable
       • Environment variable
     • Include the option to deploy Wazuh agent in the current workflows
     • For more information check the Workflows section (SPIKE - Wazuh Ansible #1461 (comment)).
3. Ansible MVP - Development of the main installation playbook(s) #1491
   • For: distributed, all-in-one, and agent.
   • Must be able to gather the custom packages URL variables (in case it exists), otherwise default values must be used.
4. Ansible MVP - Creation of the roles: wazuh-indexer, wazuh-manager, wazuh-dashboard, and wazuh-agent #1493
   • Must be able to download and install its package from a given URL.
     • First, it will be needed to download the package
     • Then, install it using the usual package manager (i.e., apt or yum)
5. Implement ansible-lint GHA action and fine tune it if it's necessary.
6. Update documentation and README