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

drop dependency on camptocamp/systemd #173

Closed
wants to merge 1 commit into from
Closed

drop dependency on camptocamp/systemd #173

wants to merge 1 commit into from

Conversation

fraenki
Copy link
Member

@fraenki fraenki commented Dec 6, 2018

Pull Request (PR) description

Currently this module depends on camptocamp/systemd, but it's only used for a single call to systemctl. A downside of using this dependency is that it may conflict with other systemd modules.

This PR replaces the need for camptocamp/systemd with a simple Exec.

@bastelfreak
Copy link
Member

Hi @fraenki. In the past we agreed on adding the dependency so we don't have to define the exec resource in each module, so this is actually on purpose. Does the resource from the systemd module conflict with another module?

@bastelfreak bastelfreak added the needs-feedback Further information is requested label Dec 25, 2018
@fraenki
Copy link
Member Author

fraenki commented Dec 31, 2018

Does the resource from the systemd module conflict with another module?

The problem is that one cannot use two modules with the same name, in this case two modules with the name systemd.

The dependency on camptocamp/systemd forces users to either use camptocamp/systemd for their systemd-related needs or to ignore the module's dependencies and workaround this locally (which is a bad idea).

This module doesn't really need all the features that camptocamp/systemd offers, it could easily be replaced, hence my proposal.

@bastelfreak
Copy link
Member

yes, namespacing in the puppet ecosystem is a long issue. I still think that the camptocamp/systemd module is the way to go. It is the approved module for systemd, so IMO this and no others should be used. Does it have any missing features? I'm happy to have a look and implement them there. Also I want to replace the ugly file resources for the unit file with the systemd::unit_file resource.

@fraenki
Copy link
Member Author

fraenki commented Feb 28, 2019

@bastelfreak Thanks for your answer! Actually yes, the camptocamp/systemd module is missing some features and convenience addons that we heavily depend on and that are present in NTTCom-MS/eyp-systemd. Especially the defined type to handle drop-ins (they use a template, so we don't have to provide our own file for every service) and the possibility to manage logind.conf. I could create feature requests in the camptocamp/systemd issue tracker if you see a chance to get these features implemented.

@Dan33l
Copy link
Member

Dan33l commented Feb 28, 2019

I agree with @bastelfreak. As supported module camptocamp/systemd should be updated instead of reinvent the wheel each time.

Are you able to implement the feature requests ?

@bastelfreak
Copy link
Member

I'm not sure if I find the free time in the near future to implement this in the camptocamp/systemd module. It would be awesome if you can provide a PR, I'm happy to review and merge it. Otherwise please open a feature request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-feedback Further information is requested
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants