Feature #5719
closedconfiguration: add a "generated by" field to suricata.yaml, to aid determine what are the correct defaults
Description
This emerged from the discussion in https://redmine.openinfosecfoundation.org/issues/5219#note-2
My understanding is that the idea is that generated by would indicate which Suricata version "created" that config, and therefore
decide what are the (main) default behaviors, for said version.
JI Updated by Jason Ish over 3 years ago
We already embed the version that generated the suricata.yaml in a comment, but thats not useful to Suricata itself. I see this looking something like:
suricata-version: 7.0.0
Then we can actually do some stuff based on that. Combined with work as-in https://github.com/OISF/suricata/pull/7528/files#diff-7b694eeeab9ec0f0da758009b2fb0dcf323de7a72a23e157e3fd66a95376f29e we could do interesting stuff. The groundwork for editions perhaps.
JF Updated by Juliana Fajardini Reichow over 3 years ago
I like the looks of this!
JI Updated by Jason Ish about 3 years ago
- Status changed from New to Rejected
Rejected as duplicate of https://redmine.openinfosecfoundation.org/issues/5822, even though this issue came first, we tracked it and committed with the other ticket ID.
JI Updated by Jason Ish about 3 years ago
- Related to Feature #5822: yaml: set suricata version in generated config added
VJ Updated by Victor Julien almost 3 years ago
- Assignee deleted (
OISF Dev) - Target version deleted (
TBD)