Thanks for all answers, I indeed want unmanaged resources to remove themselves (in some cases, I know it's somewhat dangerous). So the ensure => absent (in the package example) is not what I'm after, because that only works on managed resources. Packages that aren't mentioned anywhere in the manifest are left alone.
The "resource purge" being mentioned seems to be what I'm after. How does it work? How can I trigger it? Where to find docs and what resources have support for it? Thanks again Mathijs On Jun 17, 6:04 am, Ohad Levy <ohadl...@gmail.com> wrote: > On Thu, Jun 17, 2010 at 11:58 AM, Daniel Pittman <dan...@rimspace.net>wrote: > > > "R.I.Pienaar" <r...@devco.net> writes: > > > ----- "Daniel Pittman" <dan...@rimspace.net> wrote: > > > >> Mathijs <bluescreen...@gmail.com> writes: > > > Well, setting a default of 'ensure => absent' tells the providers that when > > something isn't listed in the manifest it should go away — which was my > > reading of the request. > > that only works for defined packages! e.g. if you do > package{"xyz":} > then it will remove it by default, it will not remove the other packages. > > > Some providers supports purging and you can purge unmanaged resources> > using > > > the resource type, but you really want to be careful with that. > > > Well, yes. You seem to be saying more or less the same thing I am, but > > disagreeing with me, and I don't quite understand where. > > The resource purge removes things which are not defined in puppet, e.g. > remove all hosts from /etc/hosts unless they are defined in puppet. > > Ohad -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.