On Thu, Apr 21, 2011 at 11:21 AM, Forrie <for...@gmail.com> wrote: > That only removes the management element, as I understand. > > I can think of a couple of scenarios where I've had issues with this: > > * ssh_authorized_keys - there is a bug where if a comment exists it > just keeps dumping more copies of the keys. When a key is no longer > managed, might be nice to have the option to edit it out. (yes I > know you can just do a file://) > > * NFS mounts. When a mount is no longer managed, I'd like to also > remove the mount point under certain conditions.
Have you looked at the Resources resource? It will let you purge unmanaged resources of a given type. http://docs.puppetlabs.com/references/latest/type.html resources This is a metatype that can manage other resource types. Any metaparams specified here will be passed on to any generated resources, so you can purge umanaged resources but set noop to true so the purging is only logged and does not actually happen. PARAMETERS NAME The name of the type to be managed. PURGE Purge unmanaged resources. This will delete any resource that is not specified in your configuration and is not required by any specified resources. Valid values are true, false. 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+$/. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
