Added new cases to test_env_variables to check some possible errors #1014
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.
Hello team,
This PR adds new cases to test_env_variables, making one of the paths configured in the env variable too long and ending with a backslash:
This way we made sure to check for the error that occurs when the expanded environment variables were longer than the maximum path allowed by the OS. We also check that even if one of those paths ends with a '' it will still be configured correctly.
Closes #999
Testing these cases in the master branch of wazuh, generate these errors:
env_variables_report.zip
We can see in the log, wrong configured paths:
Best regards.