feat(time): add optional chrony conf.d drop-ins#3
Open
Junjus wants to merge 2 commits intoSOSETH:masterfrom
Open
feat(time): add optional chrony conf.d drop-ins#3Junjus wants to merge 2 commits intoSOSETH:masterfrom
Junjus wants to merge 2 commits intoSOSETH:masterfrom
Conversation
Keep the existing /etc/chrony/chrony.conf flow unchanged so chrony.conf is still managed as before. Add optional chrony_conf_dropins and chrony_sources_dropins variables to support chrony conf.d and sources.d drop-in files. When chrony_conf_dropins_enable is set, creates the conf dropin directory and renders etc_chrony.conf as dropin. When chrony_sources_dropin_enable is set, creates the sources dropin directory and renders out sources_files Why: Debian-Trixie prefers drop-in Chrony config files, but existing hosts should keep current behavior with no migration required.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Keep the existing /etc/chrony/chrony.conf flow unchanged so chrony.conf is still managed as before.
Why:
Debian-Trixie prefers drop-in Chrony config files, but existing hosts should keep current behavior with no migration required.