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

need for specific uid/gid for Puppet user #42

Closed
Phil-Friderici opened this issue Nov 18, 2013 · 6 comments
Closed

need for specific uid/gid for Puppet user #42

Phil-Friderici opened this issue Nov 18, 2013 · 6 comments

Comments

@Phil-Friderici
Copy link
Contributor

We need to have the possibility to specify a specific uid/gid for the Puppet OS user.

@ghoneycutt
Copy link
Owner

What's the use case for this? Generally the puppet package should ensure this.

@Phil-Friderici
Copy link
Contributor Author

In our environment we need to have a fixed uid/gid number for the Puppet user account.
After seting up Puppet with this module uid/gid is both 500, which is not correct. We need to be able to specify a reserved uid/gid for the user.

@ghoneycutt
Copy link
Owner

Since you have to install puppet from the package, before running this module, I do not see how modifying this module can help. I think the package needs to be modified instead.

@Phil-Friderici
Copy link
Contributor Author

In the old template I see that the UID/GID are specified:

  user { 'puppet':
    uid        => 11111,
    gid        => 99999,
    managehome => false,
    require    => Group['puppet'],
  }
  group { 'puppet':
    gid => 99999,
  }
  class { 'old_puppet_module':
    puppettype     => client,
  }

Need to check how this looks like after installing the package before running Puppet for the first time.

@Phil-Friderici
Copy link
Contributor Author

Puppet is installed while kickstarting (eis_cm-2.7.14-1_rhel6.x86_64) with uid=498(puppet) gid=500(puppet) groups=500(puppet). A testrun with find / -gid 500 or -uid 498 didn't show any files. So it should not break anything to reset the UID/GID to the globaly reserved and used one.

I agree that the ultimate way would be to change the package. On the other side, that would mean that we can't use public available package anymore.

What about an optional paramter to activate reseting UID/GID ?

@Phil-Friderici
Copy link
Contributor Author

never mind

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