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

File resource service_overrides_template cannot be removed #710

Open
tux-o-matic opened this issue Aug 9, 2017 · 2 comments
Open

File resource service_overrides_template cannot be removed #710

tux-o-matic opened this issue Aug 9, 2017 · 2 comments

Comments

@tux-o-matic
Copy link
Contributor

Today the systemd file defined by $service_overrides_template creates a file if not set to undef.
However, if the if conditional statement is negative, it does not remove the the file.

It should be possible to control the ensure value from the File resource

@tux-o-matic tux-o-matic changed the title service_overrides_template Should clean up after itself File resource service_overrides_template cannot be removed Aug 9, 2017
@starchx
Copy link

starchx commented Aug 17, 2017

Try service_overrides_template => false This will stop from creating the file.
I had to do this because this module actually breaks default Centos7.3 Docker installation. This is my workaround:

  class { 'docker':
      use_upstream_package_source => false,
      package_name                => 'docker',
      service_overrides_template  => false, # Required as Docker module breaks default Centos Docker installation.
      service_config              => false, # Required as Docker module breaks default Centos Docker installation.
      storage_config              => false, # Required as Docker module breaks default Centos Docker installation.
    }

@tux-o-matic
Copy link
Contributor Author

@starchx as I mentioned, the problem is that the module does not clean after itself if at some point it already created the file. So setting the value to false will not help if the file was already created previously.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants