Issue #7600 has been updated by Luke Kanies.
I couldn't find record of it in email or tickets, but quite a long time ago I
recommended that we convert the 'resources' type to something that was more
oriented to group operations on unmanaged resources rather than something that
was just focused on purging.
E.g., for users, you'd do something like:
<pre>
resources { user:
ensure => absent
}
</pre>
but for services, you'd do:
<pre>
resources { service:
ensure => stopped,
enable => false
}
</pre>
But really, the problem is that it's a group operation on resources on the host
that aren't in the catalog, done using what looks like a single resource. It's
gross no matter what you do, even if the above makes it slightly more palatable.
----------------------------------------
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.
