Allow for lazy/eager systemctl daemon reloading #111
Merged
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.
Add param for
systemd::dropin_file
to allow forlazy
(the default behavior) oreager
systemctl daemon reloading.In some cases, the systemctl daemon should be reloaded before the related service is refreshed. For example, when overriding
ExecStart
. With the current behavior, it is impossible to do so if thesystemd::dropin_file
and related service are contained in the same class. There is also a potential for circular dependencies with multiple services that depend on each other and have multiple drop-in files associated with them.The new lazy option emulates the current behavior, deferring the reload until (most likely) near the end of the Puppet run. It also has the advantage of only reloading the daemon once.
The eager option allows for the daemon to be reloaded immediately after changes to the specified drop-in file, at the cost of causing multiple reloads if there are multiple
systemd::dropin_file
resources.