Refactor Ansible playbook for Wazuh agent #1516
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
YisDav
force-pushed
the
enhancement/1504-wazuh-agent-playbook-refactoring
branch
from
febe7f6 to
f959f40
Compare
YisDav
changed the title
YisDav
changed the title
YisDav
force-pushed
the
enhancement/1504-wazuh-agent-playbook-refactoring
branch
from
f959f40 to
f31e554
Compare
teddytpc1
approved these changes
Jan 28, 2025
teddytpc1
merged commit e5e590c
into
enhancement/1496-wazuh-ansible-spike-implementation-plan
10 of 18 checks passed
teddytpc1
deleted the
enhancement/1504-wazuh-agent-playbook-refactoring
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR seeks to implement the changes corresponding to the refactoring of the Ansible playbook of wazuh-agent, which allows this component to be deployed across multiple OS (Windows, Linux and MacOS).
Find more information on the related issue:
#1504