Again, this is small-shop thinking. That's not manageable with multiple diverse teams, all of whom have different needs and different ideas of what is considered safe. It also requires one additional tag to every resource, which would be easily 1000 lines in this site already and its still small.
if-else around tags would be a huge improvement. On Jun 15, 2012, at 2:40 PM, jcbollinger wrote: > 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. -- 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.
