Feature #4664
Ability to lock resources from modification
| Status: | Accepted | Start date: | 08/31/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | plumbing | |||
| Target version: | - | |||
| Affected Puppet version: | Branch: | |||
| Keywords: | ||||
| Votes: | 0 |
Description
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
History
Updated by James Turnbull over 1 year ago
- Status changed from Unreviewed to Needs Decision
- Assignee set to Luke Kanies
Updated by Luke Kanies over 1 year ago
- Status changed from Needs Decision to Accepted
- Assignee deleted (
Luke Kanies)
Great idea.
How would it integrate with ralsh? Would it?
Updated by Curtis Hawthorne over 1 year ago
Luke Kanies wrote:
How would it integrate with ralsh? Would it?
I haven’t really done much with ralsh, but I would think that if something in the locks file prevented a regular puppet run from modifying a resource/file, it should also prevent ralsh from modifying it. Or did you mean integrating in some other way?
Updated by Nigel Kersten over 1 year ago
Why is this one a good idea, and http://projects.puppetlabs.com/issues/3761 not? :)