As I keep tweaking our Puppet/Foreman setup, I was wondering if it was somehow possible to auto-magically remove uses when the associated class is removed from the server. All of our Puppet code is under source code management and requires a full change approval process to implement.
I thought of doing custom facts and then checking them against all user classes, but that seemed like it would use a ton of overhead. Another idea was to do a define that had a default of absent for a user and then pass "present" as a parameter to have the user created, but that seemed like it would still need some "magic" that most likely end up getting really deep in coding to ensure that the user didn't get pulled off a box where it needed to exist. I'm not sure this is even possible other than how I have done it in the past where I created 2 users classes. One that adds it and another that removed it. The process is a bit clunky but it does work. Anyone had any success making something like this work? -- 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/fffa2024-aeed-472e-af80-9798d7278949%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
