puppetlabs-docker icon indicating copy to clipboard operation
puppetlabs-docker copied to clipboard

Make management of systemd override directories optional

Open antaflos opened this issue 2 years ago • 7 comments

When using puppet-systemd and the systemd::dropin_file type to manage custom Docker-related overrides the puppet-systemd module takes care of creating and managing the required override directories like /etc/systemd/system/docker.service.d and /etc/systemd/system/docker.socket.d. This leads to duplicate resource declaration errors because the puppetlabs-docker module also wants to manage these systemd override directories.

This change adds a boolean parameter manage_systemd_override_dirs to control whether this module should manage the directories /etc/systemd/system/docker.service.d and /etc/systemd/system/docker.socket.d. If set to 'false' then these directories will not be touched by this module and the user must take care of managing them, e.g. by means of puppet-systemd and systemd::dropin_file. The parameter manage_systemd_override_dirs is set to 'true' by default, thus backwards-compatibility is preserved.

Contains updated spec tests and parameter documentation.

antaflos avatar Aug 12 '22 09:08 antaflos

docker is a class

Breaking changes to this file WILL impact these 18 modules (exact match):
Breaking changes to this file MAY impact these 24 modules (near match):

docker::params is a class

that may have no external impact to Forge modules.

docker::service is a class

that may have no external impact to Forge modules.

This module is declared in 6 of 579 indexed public Puppetfiles.


These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

CLA assistant check
All committers have signed the CLA.

CLAassistant avatar Aug 12 '22 09:08 CLAassistant

The Windows 2022, puppet6-nightly check fails because of network timeout issues, certainly unrelated to the changes proposed in this PR. See https://github.com/puppetlabs/puppetlabs-docker/runs/8186444366?check_suite_focus=true#step:13:73 for example. Not sure how or if I can trigger running the tests again.

antaflos avatar Sep 05 '22 11:09 antaflos

Bumping for visibility, possibly.

antaflos avatar Sep 27 '22 08:09 antaflos

Hey @antaflos thanks for that ping! Your codebase is out of date, would you mind rebasing? I will get this on the list to be reviewed at our next community day (runs most Mondays)

pmcmaw avatar Sep 27 '22 11:09 pmcmaw

Thanks @pmcmaw, I just rebased.

antaflos avatar Sep 27 '22 12:09 antaflos

Just rebased again to keep up to date. Any movement regarding this PR?

antaflos avatar Oct 17 '22 13:10 antaflos

Hi @antaflos, we have noticed this PR has been inactive for a while. An old review above by @bastelfreak suggested an alternative approach to this issue and we have agreed that it was a better solution to this problem. As such, this PR should be closed and an issue requesting that feature opened in our Issue tab here at GitHub. Thanks for your understanding.

LukasAud avatar Feb 17 '23 17:02 LukasAud

Closing inline with comments above.

jordanbreen28 avatar Apr 28 '23 15:04 jordanbreen28