Issue #14429 has been updated by Garth Kidd. Status changed from Needs More Information to Needs Decision
Andrew, the output file name depends on the target property of the Nagios_* resource. Some users want to have that depend on the host name and other facts. It's difficult to "just handle this by using a File resource" without wrapping all of our Nagios type usage in our own definitions or classes. I'm trying to work around the problem with delicately arranged notifications to execs of chmod and chown, but I'm not successfully having them run before the Nagios service notification each time. It'd be a great bloody deal easier if we could just specify the ownership and mode we need for these files. Please decide whether Nagios integration should be hard or easy. If it should be easy, please give us a way to specify mode and owernship. ---------------------------------------- Feature #14429: Naginator should provide a way to change mode, owner and group for files it writtes. https://projects.puppetlabs.com/issues/14429#change-73093 Author: Romain Vrignaud Status: Needs Decision Priority: Normal Assignee: Andrew Parker Category: Target version: Affected Puppet version: Keywords: Branch: Naginator write files with 600 mode. Nagios is run with user nagios and can't read its configuration file. I suggest that mode, owner and group be added during Naginator ressource definition. Regards, -- 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.
