Custom agent upgrade packages may be created by generating a repository to host the generated WPK files. The manager can then be set to send files to the agents from this repository.
WPK files must be named using the following pattern:
W is the version of the release,
X is the name of the operating system,
Y is the version of the operating system, and
Z is the machine’s architecture.
The structure of the repository should be as shown below:
/ └── centos └── 7 └── x86_64 ├── versions ├── wazuh_agent_v3.0.0_centos_7_x86_64.wpk └── wazuh_agent_v3.1.0_centos_7_x86_64.wpk
Every folder must contain a file named
versions that lists each version represented in the folder, along with the file’s SHA1 hash. The latest version must be placed in the first line of this file. For instance:
# cat our_wpk_repo/centos/7/x86_64/versions v3.1.0 f835015c6bbf87356a62bdfd513c7f1ffc16e0af v3.0.0 df5397c8c4a1b29c42726dfa821330fa1bac7058
This repository structure is necessary for the manager to check the agent OS, version and architecture and look for the correct upgrade package. For example, for an agent installed on Centos 7 x86_64, the manager will look for the latest package in our_wpk_repo/centos/7/x86_64/.