-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Discrepancies between \\ and / in Linux paths between WazuhDB and global-queries #29147
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
Comments
UpdateImplement function logic and UT to coverage cases. Pending to validate with the team this approach. Integration test fails due the Opensearch constrain of the ID field. |
UpdateAdjust UT and leave the issue on hold until we validate this approach |
UpdateThe new approach is make a hash of the path to SHA256, due compilation errors of the branch I'm not able to push the change proposal, that restore all previous states and implement the new design discussed with @Dwordcito |
UpdateImplement hashing solution and UT. Make rebase of the branch |
UpdateFix path entry |
UpdateWorking on Windows Registries I could find the following differences:
In this case the difference is between |
UpdateChange approach to use |
UpdateFix index field for agents prior 4.6 |
Performing tests of the functionality under development, I find that:
In WazuhDB
In GlobalQueries
Related to:
wazuh/src/wazuh_modules/inventory_harvester/src/fimInventory/fimContext.hpp
Line 657 in d75983b
Steps to reproduce
curl -k -u <indexer_user>:<indexer_pass> https://<indexer_ip>:9200/wazuh-states-files-wazuh/_search?size=10000
The text was updated successfully, but these errors were encountered: