I'll throw the question out here.
With puppet, is there a way to define a resource in such a way that when
applied to a client for the first time it is created, but if the resource
already exists on the client nothing is changed? Specifically, I'd like to
do this with users.
Here is my situation: in the past my organization has poorly managed user
UIDs across machines (multiple users in puppet with the same UID, creating
users in puppet that conflict with system users' UIDs, etc). This resulted
in numerous, frustrating UID conflicts. I've been working on cleaning this
up, but the mass renumbering of important existing users has all sorts of
production-impacting risks. What I'd like to do is tell puppet to create
these users with their new, conflict-free UIDs on new machines but have it
not touch users that are already created on existing machines. This will
allow us to use a slow, methodical approach to fixing the UIDs on old
machines to help mitigate the risks.
Any thoughts are appreciated.
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b64d9e28-e58d-46de-b1ea-a5db0b2890fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.