On Fri, Jul 3, 2015 at 4:42 PM, R.I.Pienaar <r...@devco.net> wrote: > On teardown I don't care what stays and go, just want to try my best to kill > things > > So the resources in question are varied and custom and spread over multiple > hosts. > > So rather than a specific solution that involves just killing this or that I > am > after ideas for how to do so in a generic way with any kind of resource
I don't think you'll find a clean way of doing this - you are trying to take a system that is built entirely around the concept of enforcing a desired state and telling it to "try it's best". You could do something batshit crazy with run stages but that would likely be more trouble than its worth. -- Enviatics | Automation and configuration management http://www.enviatics.com | @Enviatics Puppet Training http://www.enviatics.com/training/ -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CACxdKhEk39Voo7dQ0EXOSJxMsk5AqjwnQaPmOgqGxUJq%3Dg7g_w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
