cfg: fix config-version incosistencies #5145
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Template functions, for example, are constructed right when syslog-ng parses the configuration, so the @Version directive must be placed at the top of the config file to make it consistent.
This patch fixes the implicit "current version" mechanism (when no @Version is specified) by moving it back to the lexer, and warns the user about misplaced or redefined @Version directives.
Reproducer: Place a template("$(format-json asd=asd)" anywhere in the configuration without an explicit @Version declaration or place the @Version declaration after the config block containing the mentioned template. A compatibility warning will be produced and syslog-ng will operate in half-"compat mode".
Backport of #312 by @MrAnno