Skip to content

conf_d: merge the unbound_conf_d and conf_d params - #355

Open
b4ldr wants to merge 1 commit into
voxpupuli:masterfrom
b4ldr:342_conf_d
Open

conf_d: merge the unbound_conf_d and conf_d params#355
b4ldr wants to merge 1 commit into
voxpupuli:masterfrom
b4ldr:342_conf_d

Conversation

@b4ldr

@b4ldr b4ldr commented Dec 19, 2024

Copy link
Copy Markdown
Member

AFAICT the intention of theses two parameters is the same so lets merge them

fixes #342

@b4ldr b4ldr added the backwards-incompatible This change will lead to a major version bump for the next release label Dec 19, 2024
@b4ldr
b4ldr requested review from bastelfreak and Copilot July 21, 2025 10:27

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This pull request merges two similar parameters (unbound_conf_d and conf_d) that serve the same purpose of managing unbound configuration directories. The change consolidates functionality by removing the duplicate unbound_conf_d parameter and updating all references to use the unified conf_d parameter instead.

Key changes:

  • Removes the unbound_conf_d parameter and related purge_unbound_conf_d parameter
  • Updates all code to use conf_d and purge_conf_d consistently
  • Adds OS-specific logic to set appropriate conf_d directory paths and ownership

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
manifests/init.pp Removes duplicate parameters and updates file resource to use unified conf_d configuration
spec/classes/init_spec.rb Updates test variables and expectations to use new parameter names and adds OS-specific logic
data/os/Debian.yaml Updates Debian-specific configuration to use new parameter names and sets conf_d path
REFERENCE.md Updates documentation to reflect parameter name changes and removes deprecated parameter

Comment thread manifests/init.pp Outdated
@b4ldr
b4ldr force-pushed the 342_conf_d branch 2 times, most recently from c0e1d39 to b3f49c8 Compare July 21, 2025 10:37
AFAICT the intention of theses two parameters is the same so lets merge
them

fixes voxpupuli#342

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backwards-incompatible This change will lead to a major version bump for the next release tests-fail

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

3 participants