The file is managed by RPM - if purging is enabled, idempotency would
break after package updates place the Salt removed file back. Hence
exclude this file by managing it if it exists. In the default formula
configuration it is not included anyways.
Signed-off-by: Georg Pfuetzenreuter <mail@georg-pfuetzenreuter.net>
Pool and server configuration may have different options but it's not
currently possible.
In order to solve that, the template is changed to accept pool
or server specification as a dictionnary, specifying at least the
pool/server name and if wanted the pool/server options. If no options
are specified, it'll use chrony.options.
In order to not break anything the template is checking if the server/pool
specification is a dictionnary or not, and acts accordingly.
Fixes: #27
Signed-off-by: Arnaud Patard <apatard@hupstream.com>
* fix: restart service after config change
When chrony was already installed, the service currently does not get
restarted when the config file is changed. I added a "watch" option to
the service.running state to ensure it gets a restart when we adapt the
configuration.
* fix: replace require completely with watch to ensure service restart
Co-authored-by: Imran Iqbal <myii@users.noreply.github.com>
Co-authored-by: Imran Iqbal <myii@users.noreply.github.com>
* Run `chrony.config` as workaround
- `.config` not called by `chrony`
* Disable `fedora` for the time being due to `systemd` issue
- Refusing to accept PID outside of service control group,
acquired through unsafe symlink chain: /var/run/chrony/chronyd.pid