Wazuh-engine: Fetch policy from indexer connector #33684
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.
Closes #33519
Description
Introduces changes to the Wazuh engine to fetch policies from the indexer connector. It includes updates to the codebase for handling policy retrieval, hash checking, and existence verification.
Proposed Changes
WICdded new methods in theIWIndexerConnectorinterface for policy management.WICImplemented thegetPolicy,getPolicyHash, andexistsPolicymethods in the WIndexerConnector class, to query on wazuh-indexer.WIC: Introduced thePolicyResourcesstructure to encapsulate policy-related data.IndexerConnectorAsyncImp: AddedsearchandPoint In Timefeatures.devContainer: Modified Docker and development container configurations for testing and integrationResults and Evidence
No new test or final user feature added, but is posibble check adding this code and debugging:
Logs:
Manual tests with their corresponding evidence
Memory tests for Linux
Memory tests for Windows
Memory tests for macOS
Decoder/Rule tests (Wazuh v4.x)
runtests.pyexecuted without errorsEngine (Wazuh v5.x and above)
Wazuh server API/Framework
Artifacts Affected
Configuration Changes
Tests Introduced
Review Checklist