Modifying forward config file location about puppet-unbound HOT 4 CLOSED

Just realised this is because we have to set the config file in the forward definition, doesn't look like it's inheriting from params correctly?

from puppet-unbound.

So even if I override the config file like so:

unbound::forward:
  '.':
    forward_first: 'yes'
    config_file: "/var/unbound/conf.d/global_forward.conf"
    address:

Same issue.

from puppet-unbound.

I believe this issue is caused by the forward class using the data from the params class causing whatever setting on the unbound::config_file to be ignored. So it seems that it is not possible to override the config location, even though it looks like we aimed to do so. The later issue setting the config_file on the unbound::forward resources, there is no corresponding concat resource for the fragment, so it never gets created. So yes, this needs a fix.

from puppet-unbound.

unbound::forward now uses $config_file = $unbound::config_file so this should now work as expected, please reopen with update information if you still see an issue

from puppet-unbound.