Modify the provisioning scripts in AMI with the changes applied in the Wazuh installation assistant

[c-bordon]

related: wazuh/wazuh-installation-assistant#63

Regarding the issue, the installation assistant allows you to choose by parameter from which repository you want to install the packages.

wazuh-virtual-machines/ova/generate_ova.sh

Lines 232 to 238 in 192030f

	BUILDER_ARGS="-i"
	if [[ "${PACKAGES_REPOSITORY}" == "dev" ]]; then
	BUILDER_ARGS+=" -d"
	elif [[ "${PACKAGES_REPOSITORY}" == "staging" ]]; then
	BUILDER_ARGS+=" -d staging"
	fi

wazuh-virtual-machines/ova/generate_ova.sh

Line 256 in 192030f

bash builder.sh ${BUILDER_ARGS}

Tasks

• Update Workflow and Workflow script to the new logic
• Remove WAZUH_VIRTUAL_MACHINES_REFERENCE input
• Change SUFFIX_AMI input to AMI_REVISION
• Test Build AMI workflow

Important

The AMI_REVISION input must have a numeric format like wazuh-4.10.0-1 it is reserved for AMI candidates, to build a development AMI use another revision format, like -dev

[jnasselle]

Update

Please consider the next information, because our package generation script needs an undocumented mandatory input field and behaviors.

Specs:

• Name (proposal. SHOULD HAVE ID)

run-name: Build AMI ${{ inputs.id }}

• Inputs

      id:
        type: string
        required: false

      id:
        type: string
        description: |
          ID used to identify the workflow uniquely.
        required: false

[Enaraque]

Update report

The changes related to the installation of Wazuh (Related: wazuh/wazuh-installation-assistant#63) on the AMI have been made in the playbook.
Additionally, necessary updates have been made to the workflow:

• The input id has been added.
• The input WAZUH_VIRTUAL_MACHINES_REFERENCE has been changed to be used as an environment variable.
• The input name SUFFIX_AMI has been modified to AMI_REVISION.

Testing

Workflow execution

All these changes have been tested by running the following workflow, which completed successfully:

• https://github.com/wazuh/wazuh-virtual-machines/actions/runs/11030325119

AMI installation

After running the workflow, if we create an instance with the generated AMI, we can see that the packages are installed, and the dashboard is accessible without any issues.

$ ssh -i test-wvm-48-AMI.pem -p 2200 [email protected]
Last login: Wed Sep 25 10:39:56 2024 from XX.XX.XX.XX


wwwwww.           wwwwwww.          wwwwwww.
wwwwwww.          wwwwwww.          wwwwwww.
 wwwwww.         wwwwwwwww.        wwwwwww.
 wwwwwww.        wwwwwwwww.        wwwwwww.
  wwwwww.       wwwwwwwwwww.      wwwwwww.
  wwwwwww.      wwwwwwwwwww.      wwwwwww.
   wwwwww.     wwwwww.wwwwww.    wwwwwww.
   wwwwwww.    wwwww. wwwwww.    wwwwwww.
    wwwwww.   wwwwww.  wwwwww.  wwwwwww.
    wwwwwww.  wwwww.   wwwwww.  wwwwwww.
     wwwwww. wwwwww.    wwwwww.wwwwwww.
     wwwwwww.wwwww.     wwwwww.wwwwwww.
      wwwwwwwwwwww.      wwwwwwwwwwww.
      wwwwwwwwwww.       wwwwwwwwwwww.      oooooo
       wwwwwwwwww.        wwwwwwwwww.      oooooooo
       wwwwwwwww.         wwwwwwwwww.     oooooooooo
        wwwwwwww.          wwwwwwww.      oooooooooo
        wwwwwww.           wwwwwwww.       oooooooo
         wwwwww.            wwwwww.         oooooo


         WAZUH Open Source Security Platform
                  https://wazuh.com/


[wazuh-user@wazuh-server ~]$ rpm -qa | grep wazuh
wazuh-indexer-4.9.0-1.x86_64
wazuh-manager-4.9.0-1.x86_64
wazuh-dashboard-4.9.0-2.x86_64