Feature #4783
closedTask #4780: tracking config: configuration usability improvements
config/yaml: Allow fully qualified configuration keys (top.sub.sub: value)
Description
Includes in our configuration file completely override the keys they override, in some cases it might be nice to just do the following in an include:
vars.address-groups.HOME_NET: "7.1.2.3/32"
Note, in some cases this might already work as its available with the --set command line option, however, working like this in a configuration file is not official.
This is also very convenient in configuration files that are included.
This also seems to be common in YAML configurations in tools created in Go (filebeat, I think some docker tools). I'm not sure if this is an aspect the YAML parsers in Go, or just a common conventions in "cloud" apps. But still useful.
JI Updated by Jason Ish over 4 years ago
- Tracker changed from Task to Feature
VJ Updated by Victor Julien over 4 years ago
- Subject changed from Allow fully qualified configuration keys (top.sub.sub: value) to config/yaml: Allow fully qualified configuration keys (top.sub.sub: value)
JI Updated by Jason Ish over 3 years ago
- Status changed from New to Assigned
- Assignee set to Jason Ish
JI Updated by Jason Ish over 3 years ago
- Status changed from Assigned to In Review
After a quick look this looked rather easy to do as we had most of the support code already.
PR for review: https://github.com/OISF/suricata/pull/8439
JI Updated by Jason Ish over 3 years ago
- Status changed from In Review to Closed
- Target version set to 7.0.0-rc1
JI Updated by Jason Ish 10 days ago
- Related to Documentation #8738: config: document support for dotted configuration keys in YAML added