-
Notifications
You must be signed in to change notification settings - Fork 468
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
[cscli] We added patterns_dir option to config.yaml but isnt used in hubtest #3182
Comments
@LaurenceJJones: Thanks for opening an issue, it is currently awaiting triage. In the meantime, you can:
DetailsI am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository. |
@buixor Please reconsider this value assignment. If anybody plans to follow https://docs.crowdsec.net/docs/parsers/create and create their own parser, they will end up frustrated here. Alternatively, as IIRC you need to run |
To aid with debugging it these codes right here: crowdsec/pkg/hubtest/hubtest_item.go Lines 598 to 603 in d8bc17b
crowdsec/pkg/hubtest/hubtest_item.go Lines 419 to 424 in d8bc17b
It only get the default values and doesnt look at the parsed configuration. |
What happened?
When setting a custom
patterns_dir
in config.yaml and usingcscli hubtest run --all
the patterns dir is not usedconfig.yaml
This is used within the test_env.sh script to not need crowdsec to be installed.
What did you expect to happen?
The
pattern_dir
options to be respectedHow can we reproduce it (as minimally and precisely as possible)?
Prep the test folder:
Edit
config/dev.yaml
and add the following:Anything else we need to know?
No response
Crowdsec version
OS version
Enabled collections and parsers
Acquisition config
On Windows:
C:> Get-Content C:\ProgramData\CrowdSec\config\acquis.yaml
paste output here
Config show
Prometheus metrics
Related custom configs versions (if applicable) : notification plugins, custom scenarios, parsers etc.
The text was updated successfully, but these errors were encountered: