On Friday, June 15, 2012 1:36:41 PM UTC-5, Jo wrote: > > 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. >
No, but you don't need that for this purpose. > 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. > What you describe would indeed be unreasonably difficult to maintain, but you don't need to do that. You can instead assign some for-purpose tag of your choosing (e.g. "safe") to all resources you consider safe to modify at any time. Then you only have to worry about that one tag. Moreover, you then control what is considered safe from your manifests, instead of from nodes' local config files, and you can even switch safety on and off for specific resources if you should ever need to do. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/6BaMhZBvO60J. 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.
