Update the AL2023 box used for OVA build process in the S3 bucket

[Enaraque]

Description

In the local OVA build process, a custom Vagrantfile is used. This file references a box based on AL2023, created by Wazuh and stored in S3 at s3://packages-dev.wazuh.com/vms/ova/.

wazuh-virtual-machines/ova/Vagrantfile

Line 6 in a178f10

config.vm.box_url = "https://packages-dev.wazuh.com/vms/ova/al2023.box"

However, this box is not being updated when a new OVA is generated for each release. As a result, the box used locally may be outdated and not match the one used in the production OVA.

Although the box is built during the OVA creation process, it is not currently being uploaded to S3. It is necessary to upload the box to S3 alongside the OVA image so that users building the OVA locally can use the exact same box that was used to generate the production OVA.

[CarlosALgit]

Update Report

I have changed the PreConfigurer function that prepares the wazuh-virtual-machines directory to be used by the CoreConfigurer, Provisioner and PostConfigurer. This function deletes all unnecessary files from the directory to make the process faster. An exception has been added to leave the al2023.box file so that it can later be uploaded to AWS S3.

I have also started to modify what is needed in the workflow to upload the Vagrant Box to the bucket.

[CarlosALgit]

Update Report

Today I made the changes to the workflow to upload the Vagrant box to the S3 bucket and when testing here it gave an error. I assume it is a permissions error, because the path seems to be correct. I want to investigate also what happens if you try to upload a file that already exists in the bucket, could that be the reason for the error.