No insistence on unit_entry ever or service_entry with absent manage_unit #345
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.
Pull Request (PR) description
Removing a unit file with
systemd::manage_unit
with the following:This is not possible and a
service_entry
andunit_entry
must be specified as the unit nameis in the service namespace.
Remove insistence for
unit_entry
andservice_name
parameter for the absent case.For the
ensure => 'present`` the
unit_entryis no longer required since it is perfectly possible to create units without any
[Unit]` section.Also improve failure message when
service_entry
is not specified for service unit.