Hi Guys, I''m trying to get this done but don''t know how to get there: Puppet is used to manage a new webserver using nginx+php-fpm , on which each website has it''s own user which is used to run the php-fpm pool. Sure I can add users to the manifest so site foo.bar.tld will get a user foo_bar_tld... that''s fine. I also create a directory in the webroot, and define the webroot as a directory which has to be purged by puppet. This is done to make sure that if a website leaves, all files will be removed (the php/nginx configs are being removed as well). But how can I do this for users? There''s no such thing as purge => true for users, and afaik I can''t import more files into /etc/password (which *can* be purged after removing the site). This complete machine is being managed by puppet so I don''t have to take other users etc into account. Does anyone know a smart trick for doing this? Cheers, Boudewijn Ector -- 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 puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
The “trick” is setting ( ensure => absent, ) for the users you want to purge. How you do that depends on how you set it up to begin with. On Oct 9, 2013, at 5:13 PM, Boudewijn Ector wrote:> Hi Guys, > > > I''m trying to get this done but don''t know how to get there: > > > Puppet is used to manage a new webserver using nginx+php-fpm , on which each website has it''s own user which is used to run the php-fpm pool. Sure I can add users to the manifest so site foo.bar.tld will get a user foo_bar_tld... that''s fine. > I also create a directory in the webroot, and define the webroot as a directory which has to be purged by puppet. > This is done to make sure that if a website leaves, all files will be removed (the php/nginx configs are being removed as well). > > But how can I do this for users? There''s no such thing as purge => true for users, and afaik I can''t import more files into /etc/password (which *can* be purged after removing the site). This complete machine is being managed by puppet so I don''t have to take other users etc into account. > > Does anyone know a smart trick for doing this? > > Cheers, > > Boudewijn Ector > > -- > 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 puppet-users+unsubscribe@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out.-- 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 puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Also, to purge users, you say
resources { ‘user’:
purge => true,
unless_system_user => ... # This keeps system users from being purged.
# By default, it does not purge users whose UIDs
are less than or equal to 500,
# but you can specify a different UID as the
inclusive limit.
# Valid values are true, false. Values can match
/^\d+$/.
}
http://docs.puppetlabs.com/references/latest/type.html#resources
On Oct 9, 2013, at 6:54 PM, Dan White wrote:
> The “trick” is setting ( ensure => absent, ) for the users you want to
purge.
>
> How you do that depends on how you set it up to begin with.
>
> On Oct 9, 2013, at 5:13 PM, Boudewijn Ector wrote:
>
>> Hi Guys,
>>
>>
>> I''m trying to get this done but don''t know how to
get there:
>>
>>
>> Puppet is used to manage a new webserver using nginx+php-fpm , on which
each website has it''s own user which is used to run the php-fpm pool.
Sure I can add users to the manifest so site foo.bar.tld will get a user
foo_bar_tld... that''s fine.
>> I also create a directory in the webroot, and define the webroot as a
directory which has to be purged by puppet.
>> This is done to make sure that if a website leaves, all files will be
removed (the php/nginx configs are being removed as well).
>>
>> But how can I do this for users? There''s no such thing as
purge => true for users, and afaik I can''t import more files into
/etc/password (which *can* be purged after removing the site). This complete
machine is being managed by puppet so I don''t have to take other users
etc into account.
>>
>> Does anyone know a smart trick for doing this?
>>
>> Cheers,
>>
>> Boudewijn Ector
--
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 puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.