On Wednesday, February 6, 2013 5:40:41 AM UTC-8, llowder wrote: > > > > On Wednesday, February 6, 2013 6:06:49 AM UTC-6, Ken Barber wrote: >> >> Perhaps you want to use 'puppet node deactivate' for now: >> >> >> http://docs.puppetlabs.com/puppetdb/1.1/maintain_and_tune.html#deactivate-decommissioned-nodes >> >> >> This will at least remove it from being collected immediately, but it >> leaves it in the database. >> >> So beyond that we are working on an automated clean mechanism in >> PuppetDB: https://projects.puppetlabs.com/issues/18682#change-82618 >> ... which as you can see is in code review right now. If all goes well >> this should be in a release coming to your cinemas soon ... :-). >> >> ken. >> > > > I would also take a look at > https://ask.puppetlabs.com/question/88/how-can-i-purge-exported-resources-from-puppetdb/which > discusses this same issue and has a couple of alternatives, though > YMMV, emptor caveat and all that type of thing. > >> >> Yes you sent me that before, earlier on the thread =)
Those tips work just fine and I've baked them into my scripts. However I had read that "puppet node clean" was scheduled to be "fixed" in 3.1 and it isn't so I wanted to make sure I wasn't doing something else wrong. -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
