Issue #4664 has been reported by Curtis Hawthorne. ---------------------------------------- Feature #4664: Ability to lock resources from modification http://projects.puppetlabs.com/issues/4664
Author: Curtis Hawthorne Status: Unreviewed Priority: Normal Assignee: Category: plumbing Target version: Affected version: Keywords: Branch: How about a file $libdir/locks that lists either resources (//class::nested/File[my_config]) or files (/etc/my/config) on which puppet is not allowed to perform any actions. If puppet is prevented from doing something by this file, that could be logged as a failure or just a regular log messages (configurable). Thoughts? If this seems like a good idea, I wouldn't mind taking a stab at it myself. This is based on the comments in #3761 and http://groups.google.com/group/puppet-users/browse_frm/thread/b2bc8b70d7c49a9a -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
