Closed dani closed 3 years ago
Hello @dani !
Yes, this is something that will be coming soon, we're going to soon publish a proposal and I will be sure to highlight you to get some feedback :+1:
(note: it is likely to be something inspired from rfc6902 with some user-friendly sugar coating on top. the idea is to make it trivial to use yet powerful enough.)
Hello @dani,
This thread https://discourse.crowdsec.net/t/request-for-comments-parsers-scenarios-customization-in-the-crowdsec-agent/129 is exactly about that, your feedback would be welcomed !
Closing this one as it should be solved by https://github.com/crowdsecurity/crowdsec/issues/660
when installing parsers and decisions from the hub, all values (especially buckets capacity and leakspeed) are "hardcoded". It'd be great to have some kind of variable support so I could override those values locally, without having to fork the entire scenario from the hub.
Eg
Then in eg /etc/crowdsec/variables.yml, I could override those with
And those values would take precedence over the variables set in the scenario.