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

RFE - Support for DNS Service record configuration #131

Open
EPK-nl opened this issue Nov 2, 2021 · 1 comment
Open

RFE - Support for DNS Service record configuration #131

EPK-nl opened this issue Nov 2, 2021 · 1 comment

Comments

@EPK-nl
Copy link

EPK-nl commented Nov 2, 2021

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 3.7
  • Ruby:
  • Distribution: RHEL 7 & 8
  • Module version: v2.0.0

How to reproduce (e.g Puppet code you use)

There is no support for the dynamic configuration of chrony.

What are you seeing

A missing parameter and corresponding functionality

What behaviour did you expect instead

The possibility to specify a list of DNS Service records containing the NTP service records.

Output log

None, as the functionality is missing.

Any additional information you'd like to impart

The code I created outside of the module to support the required functionality:

  # Support for dynamic configuration is not supported by the module (yet), so we configure it here.
  $dnssrv_records.each | String $srv_record | {
    exec { "chronyc-enable-${srv_record}":
      command => "/usr/libexec/chrony-helper enable-dnssrv ${srv_record}",
      unless  => "/bin/test -f /etc/systemd/system/timers.target.wants/chrony-dnssrv@${srv_record}.timer",
    }
  }

This does the trick, but should be in the module.
The current test for the existence of the timer file should be replaced by matching the output of /usr/lib/chrony-helper list-dnssrv when this is in the module, allowing the removal of dynamic entries when they are no longer in the list.

@jcpunk
Copy link
Contributor

jcpunk commented Jul 15, 2022

It looks like chrony-helper is dropped in Fedora.... do we know how this is fairing upstream?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants