Let's say that I'm deploying a steady stream of identical hosts. Each has some piece of SW on it that's managed by Puppet. I continue to (regularly) add to and maintain this group over time.
Day comes when this SW is no longer required. So I remove the module from Puppet to prevent it being included on future hosts in this group. "What about the existing hosts?" I ask. "Add a module to remove the SW" I think. "What about the future hosts? Won't this seem a bit odd to tell puppet to remove SW that was never installed?" I wonder. "Puppet is idempotent!" says the FM. "Ok - but it still seems amiss. To a 'distant observer' it would seem an odd practice." says I. Should I break up the 'before' and 'after' hosts into separate groups / environments? I use an ENC to manage the modules. Maybe a DB entry to indicate who gets the extra module? Some other pathway? -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7cf584ad-b697-4904-8428-9750a1444a93%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
