You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having an "include:" line in places in the server: stanza with newer versions of unbound (started with unbound-1.16.2-5.el8_9.6 in ol8 appstream, but also happens with the latest 1.20 version i compiled) will error out upon configcheck.
What behaviour did you expect instead
It'd be nice to have a dedicated module command to set the include: directive outside of the server stanza, in its own stanza like the example config for unbound.conf does:
# Use this anywhere in the file to include other text into this file.
#include: "otherfile.conf"
# Use this anywhere in the file to include other text, that explicitly starts a
# clause, into this file. Text after this directive needs to start a clause.
#include-toplevel: "otherfile.conf"
# The server clause sets the main parameters.
server:
# whitespace is not necessary, but looks cleaner.
Output log
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered:
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
inside of a yaml:
What are you seeing
Having an "include:" line in places in the server: stanza with newer versions of unbound (started with unbound-1.16.2-5.el8_9.6 in ol8 appstream, but also happens with the latest 1.20 version i compiled) will error out upon configcheck.
What behaviour did you expect instead
It'd be nice to have a dedicated module command to set the include: directive outside of the server stanza, in its own stanza like the example config for unbound.conf does:
https://github.com/NLnetLabs/unbound/blob/master/doc/example.conf.in
Output log
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered: