unbound_version not set on first run causing unexpected config file setting about puppet-unbound HOT 1 CLOSED

A potential fix could be to use a different variable in the template which is set after the package has been installed by running unbound -V at that point

We can not do this due to the way puppet works*. Facts are calculated before any of the puppet catalog is applied as such we have the the following flow

• facts collected (unbound not installed so no way to get version)
• first puppet run and we install unbound
• next puppet run unbound_version is available
  This unfortunately is a known issue. either we install all config items and break unbound for anyone not running the most recent version of ubound we support. or we configure things like this and we need to puppet runs to get a correct unbound.conf file.

Definitely open to suggestion to improve this as its a common pattern

for this specific config we can probably write it always. ill have a check of metadata.json and update the minimum version of unbound we support

*we could possibly used some type of deferred function but im only on puppet 5 so havn't had a chance to play with them

from puppet-unbound.