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

The group (in the /etc/wireguard/ permissions) should not be hard coded. #97

Open
NiklausHofer opened this issue Dec 28, 2023 · 1 comment
Labels
good first issue Good for newcomers

Comments

@NiklausHofer
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: all
  • Ruby: all
  • Distribution: Gentoo
  • Module version: 4.0.0

How to reproduce (e.g Puppet code you use)

  • Use the role on a system without systemd

What are you seeing

Error: /Stage[main]/Wireguard/File[/etc/wireguard]/group: change from 'root' to 'systemd-network' failed: Could not find group systemd-network

What behaviour did you expect instead

It would be better if the group was not hardcoded.

Output log

Error: /Stage[main]/Wireguard/File[/etc/wireguard]/group: change from 'root' to 'systemd-network' failed: Could not find group systemd-network
@smortex smortex added the good first issue Good for newcomers label Dec 29, 2023
@smortex
Copy link
Member

smortex commented Dec 29, 2023

That should probably by a system dependent default value, e.g. root and a specific group on some operating systems thanks to a Hiera override.

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

No branches or pull requests

2 participants