https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291357
--- Comment #4 from Leonid Evdokimov <[email protected]> --- (In reply to crest from comment #3) I plan to keep it as (id, rule, label, counters). I'm unaware of a use-case that benefits from splitting ${rule} into bits and justifies extra effort. My two agenda points are stats/monitoring & table updates automation. Is there a good reason to rewrite anchor in an semi-unattended way? I mean, I expect `Serializer | sed | Deserializer` to be equally good in most cases, the output still needs a review by a pair of eyes equipped with `diff`. Am I missing something? I'm not a heavy pf(4) user, just a maintainer of a dozen of OPNsense boxes — so I don't know how pf evolved over time within FreeBSD codebase, how it was extended, if rule format was changed, what were API/ABI guarantees, and so on. That's why I also don't feel I'm the right person to craft a pf.conf.json & pf.conf.xml format :-) -- You are receiving this mail because: You are the assignee for the bug.
