Issue #10113 has been updated by Nick Lewis.
puppet.conf type with 280 properties! We already have the ability to a) read a config file, and b) generate a config file. It shouldn't be too hard to piece those two bits of code together, if we had some resource type that took a setting name and value. Perhaps with the complications of comment, and that we'd rather not read and write the file for *each* change, but also can't really use parsed file for this. ---------------------------------------- Feature #10113: It should be easier to manage puppet configuration files with puppet https://projects.puppetlabs.com/issues/10113 Author: Nigel Kersten Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: Puppet should have native support at a high level for managing internal settings on agents. This includes all the .conf files, particularly puppet.conf. You shouldn't have to require that an entire puppet.conf.erb be used to manage the settings, you should be able to idempotently manage single settings. If this were modelled entirely as puppet resources, then we could use the resources resource to optionally purge undefined settings. -- 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 puppet-bugs@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
