Improving the way configuration options are handled

[therobot]

PowerDNS refuses to start if there is a backend specific option and that backend is not installed.

Currently default attributes such as node['authoritative']['config']['pipe_command'] make the server refuse to start when installing other backends but not pipe backend.

A more intelligent way of dealing with this behavior is desired.

[tarak]

+1. Forking it is...

[martinisoft]

@tarak If you happen to come up with a patch, please submit a pull request 👍

[aeden]

I believe the consensus in the powerdns IRC channel was to default to the bind backend.

[tarak]

@martinisoft I would just delete the line

default['pdns']['authoritative']['config']['pipe_command'] = '/opt/pdns-3.4.1/modules/pipebackend/backend.pl'

in the file

attributes/authoritative.rb

I think the best way to use this cookbook is to document the requirement of setting the attribute

default['pdns']['authoritative']['config']['launch']

to the appropriate backend that one wants to use. I do this in a wrapper cookbook and, in my case, this is where I configure the gpgsql backend. If you still want a PR please confirm...

[therobot]

I'm closing this issue, the newest 3.0 version on the cookbook provides a new way of configuring PowerDNS which deprecates this method.