Actions
Feature #3290
openuse config vars everywhere
Description
The address and port vars are currently limited to specific uses. E.g. port vars can be in rules and in the vxlan config.
Maybe it would make sense to take a much simpler approach. Treat the vars more like macros in C, where the cpp simply replaces the macros with their value before the compiler compiles it.
Updated by Jason Ish about 5 years ago
Victor Julien wrote:
Maybe it would make sense to take a much simpler approach. Treat the vars more like macros in C, where the cpp simply replaces the macros with their value before the compiler compiles it.
I 100% agree. So just a simpler vars section maybe?
vars: FILE_DATA_PORTS: "[$HTTP_PORTS,110,143]"
(of course keeping support for the "groups" we already have).
Updated by Victor Julien about 5 years ago
- Assignee set to OISF Dev
- Target version set to 6.0.0beta1
Yeah I think this makes sense.
Updated by Victor Julien over 4 years ago
- Target version changed from 6.0.0beta1 to 7.0.0-beta1
Updated by Victor Julien about 4 years ago
- Target version changed from 7.0.0-beta1 to TBD
Actions