Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

$conf_d and $unbound_conf_d are not documented and unclear how they differ beyond their location #342

Open
arusso opened this issue May 6, 2024 · 2 comments · May be fixed by #355
Open
Labels
docs Improvements or additions to documentation

Comments

@arusso
Copy link

arusso commented May 6, 2024

I'm trying to understand the difference between the undocumented $conf_d and $unbound_conf_d parameters of the unbound class. Neither seems to be used anywhere outside of ensuring directory ownership (but not included in the configuration by default), and in the case of the $unbound_conf_d directory, you can also ensure the directory is purged of unmanaged configurations.

Can we get these parameters documented based on the intended usage?

@TheMeier TheMeier added the docs Improvements or additions to documentation label May 7, 2024
@Valantin
Copy link

Valantin commented May 9, 2024

I'm not sure, but a possible explaination was:
unbound_conf_d is the default directory for many OS packages with precondigured configuration, the module purge the content.
conf_d I assume is a directory with not managed configuration we want to use, the module create it by default but not include it in the configuration

@b4ldr
Copy link
Member

b4ldr commented Aug 29, 2024

Looking through the history i think theses parameters probably point to the same thing but are perhaps different on different distros. The commit that introduced the conf_d directory mentions SuSE support. and the PR (#225) that added $unbound_conf_d mentions Debian so we can probablly merge theses two parameters but would need to know what the defaults are for each supported distro

b4ldr added a commit to b4ldr/puppet-unbound that referenced this issue Aug 29, 2024
AFAICT the intention of theses two parameters is the same so lets merge
them

fixes voxpupuli#342
b4ldr added a commit to b4ldr/puppet-unbound that referenced this issue Nov 21, 2024
AFAICT the intention of theses two parameters is the same so lets merge
them

fixes voxpupuli#342
b4ldr added a commit to b4ldr/puppet-unbound that referenced this issue Nov 21, 2024
AFAICT the intention of theses two parameters is the same so lets merge
them

fixes voxpupuli#342
b4ldr added a commit to b4ldr/puppet-unbound that referenced this issue Nov 21, 2024
AFAICT the intention of theses two parameters is the same so lets merge
them

fixes voxpupuli#342
b4ldr added a commit to b4ldr/puppet-unbound that referenced this issue Nov 21, 2024
AFAICT the intention of theses two parameters is the same so lets merge
them

fixes voxpupuli#342
b4ldr added a commit to b4ldr/puppet-unbound that referenced this issue Nov 21, 2024
AFAICT the intention of theses two parameters is the same so lets merge
them

fixes voxpupuli#342
b4ldr added a commit to b4ldr/puppet-unbound that referenced this issue Dec 19, 2024
AFAICT the intention of theses two parameters is the same so lets merge
them

fixes voxpupuli#342
b4ldr added a commit to b4ldr/puppet-unbound that referenced this issue Dec 19, 2024
AFAICT the intention of theses two parameters is the same so lets merge
them

fixes voxpupuli#342
@b4ldr b4ldr linked a pull request Dec 19, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to documentation
Projects
None yet
4 participants