-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adapt agent package generation workflows with VPN and allocator module #22839
Comments
Update 10/04/2024
|
Update 16/04/2024
|
StatusIn progressBecause we are working on the unlocked parts of both Still blockedPlease note that it is still blocked due to lack of provisioning of |
Update 17/04/2024Thread with comments: https://wazuh-team.slack.com/archives/C06Q9QHP0QP/p1713349465431879 |
Updates:(30/04/2024): Implemented allocator usage in |
Update 06/05/2024I continue testing workflows related to Windows and macOS:
|
Update 07/05/2024
|
Update 08/05/2024
|
Update 09/05/2024
|
Description
This issue is to work on the packet generation workflows that need the Wazuh VPN and the use of the allocator module for special machines (arm and macOS/windows signatures).
After migrating those workflows, for security reasons, to the private repo in this issue: https://github.com/wazuh/wazuh-agent-packages/issues/1
This issue is going to be used to reference the PRs in the private repo that introduce the necessary steps to have the packages complete.
Tasks
Blocked by
The text was updated successfully, but these errors were encountered: