On Jun 15, 2012, at 7:16 AM, jcbollinger wrote: > You could conceivably combine that general idea with tags, so as to apply > only changes considered safe on most puppet runs, but allow everything to be > applied together in maintenance windows. Getting the tags (only) in the > right places could be tricky, and you would need to carefully weigh the > consequences, but it should be possible to do what you want this way.
Unfortunately you can't use tags to limit whether or not something happens. I have a bug open on this. I'd love to say "only take this action when a tag is set" but this doesn't work. The only thing you can do is put *EVERY* tag inside the puppet.conf for every host except the tags you want to use to limit actions. At even this fairly small install I'm working on right now, the total tag list is well over 200 entries and growing 8-10 a day. Maintaining that tag list for puppet.conf isn't impossible, but would be very difficult. It's very bizarre in that we have a function tagged() but it only checks if the resource itself is tagged a certain way. I suspect this is only useful in defines which can be called from multiple points. http://projects.puppetlabs.com/issues/11148 -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- 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.
