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.
Hi all,
I imagine rewrites of existing formulas are not taken lightly, and they shouldn't.
There were many great idea's taken from the current formula, which will still work. Some things did change that makes this PR not backward compatible with current pillar.
This is an initial PR, i'd very much like some feedback on if we want this at all, and possible improvements. See todo below.
So, what does this bring? Some of these items are also present in the current version.
option domain-name-servers
allow
,deny
,set
, `match, etc are repeated when values are in list formprimary
, are not printed forsecondary
roleIncompatibility with the current formula:
option <something>
statements require to be set underoptions:
dictcustomized_options
->custom_options
Todo:
Probably forgot to mention several things.
This was quite a bit of work, especially the jinja code, getting to the eventual imports / macro combination as a solution for dealing with the blocks, custom option tracking, and passing configuration.
Hope you like!