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

make config_keys option optional #156

Merged
merged 1 commit into from
Aug 11, 2022
Merged

Conversation

bastelfreak
Copy link
Member

Previously we always wrote keyfile to the chrony configuration file.
This is not always desired. To not cause a breaking change but still
make this configureable, the parameter is now a variant. Besides passing
an absolute path, you can now set it to '' (empty string). If that's
the case, the keys file won't be managed by Puppet and the option will
be removed from the config file.

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

@bastelfreak bastelfreak added the enhancement New feature or request label Jul 19, 2022
@bastelfreak bastelfreak self-assigned this Jul 19, 2022
@bastelfreak bastelfreak marked this pull request as ready for review July 19, 2022 07:12
@bastelfreak
Copy link
Member Author

still a draft, but I wanted to have CI.

Previously we always wrote `keyfile` to the chrony configuration file.
This is not always desired. To not cause a breaking change but still
make this configureable, the parameter is now a variant. Besides passing
an absolute path, you can now set it to `''` (empty string). If that's
the case, the keys file won't be managed by Puppet and the option will
be removed from the config file.
@bastelfreak
Copy link
Member Author

not a draft anymore :)

@bastelfreak bastelfreak merged commit ed3dad8 into voxpupuli:master Aug 11, 2022
@bastelfreak bastelfreak deleted the keyfile branch August 11, 2022 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants