Issue #7600 has been updated by Luke Kanies.
Daniel Pittman wrote:
> Stefan Schulte wrote:
> > IIRC `resource { 'mytype': purge => true }` works for every provider that
> > has an `instances` method. I dont know if this can work for all types:
> >
> > * How should purging files behave? Delete ALL files I dont manage with
> > puppet?
>
> Yes.
This is unreasonable, IMO. File purging is only reasonable with a base
directory.
> > * How should purging services behave? Stop all running and unmanaged
> > services?
>
> Yes.
>
> > * Purging ssh_authorized_key: ssh-keys can be stored in different files
> > (unlike host entries). Should puppet go through all possible
> > homedirectories searching for keyfiles to delete entries there?
>
> Ideally, but I wouldn't die to learn that the provider wasn't sophisticated
> enough to identify that ... which is certainly a bug from the "inspect the
> content of this system" side of things.
The way this is done now is to track default locations for these types, along
with all locations we're managing any instances of the type. This is a pretty
good effort for this, and I think suffices for the long term.
> > I also see a problem with the current approach of using an extra type
> > (`resources`) for purging: Every type may have some need to exclude stuff.
>
> I don't see why an extra declaration is desired, compared to just setting the
> default `ensure => absent` or whatever at the top level. I also don't see
> that we should try and maintain some "exclude" list of things to never purge,
> even though we were told to. That leads to a proliferation of "no, really,
> do what I said" instructions at some point.
There's system-user support in user purging (that is, do not purge users whose
IDs are below a given value) right now and I think people are quite fond of it,
and it certainly makes sense to provide something like this as a knob.
> > You dont want to erase system users by default
>
> Even if they are explicitly specified? I needed to do that back when we
> migrated our Nagios user to LDAP from /etc/passwd – or do you mean just when
> we are handling global purging?
He said 'by default'.
----------------------------------------
Feature #7600: Need ability to remove all unmanaged resources
https://projects.puppetlabs.com/issues/7600
Author: Randall Hansen
Status: Investigating
Priority: Normal
Assignee:
Category:
Target version:
Affected Puppet version:
Keywords: puppetcamp-eu-2011
Branch:
This works, purging all unmanaged hosts entries:
resources { 'host':
purge => true,
noop => true,
}
We should have a similar property for all (most?) types.
--
*This ticket is a request for comment, coming out of a discussion at Puppet
Camp EU, 2011. No promises whatever about implementation, but there were
enough people interested to open a public discussion.*
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
