System tests: Add provision capabilities to deployment tool in AWS environment

[Rebits]

Related issues
#2787

Development branches

Wazuh-qa
2796-provisioning-tool-4.4

Wazuh-Jenkins
2796-provisioning-tool-4.4

Note: Changes in wazuh-jenkins and wazuh-qa will be eventually merged in the master branch too.

Wazuh-Ansible
2796-provisioning-tool-4.4

Description

The #2788 development allows the deployment of a custom environment.
In order to launch system tests, we need to include provisioning capabilities in the newly developed tool.

Requirements

For system testing is required the necessary provisioning tasks are:

• Installation of QA framework
• Installation of Wazuh (Agent or manager)
• Cluster deployment
• Agent registration
• Wazuh initialization

This provisioning only requires the following information, obtained through pipeline parameters:

• Infrastructure's information (System tests: Deployment file design #2789)
• Package to be tested
• QA branch

We need to take into account that this provisioning phase should be different from the required for a specific system test (register all the agents into a worker, add configuration to a specific manager, etc). This kind of provision should be included in a suite of fixtures.

For this reason, I suggest the following convention:

• Generic ansible playbooks should be placed in the wazuh-qa repository
• By default, the agents should be registered in the master node
• All the wazuh ips should be stored in the /etc/hosts file
• Initial status of all the environment is running