Naginator should provide a way to change mode, owner and group for files it writtes.
|Assignee:||Andrew Parker||% Done:|
|Affected Puppet version:||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.
#1 Updated by Andrew Parker about 1 year ago
- Status changed from Unreviewed to Needs More Information
- Assignee set to Andrew Parker
You should probably just handle this by using a File resource that depends on you nagios resource that can set the permissions as you need. You can, and probably should, encapsulate this in a defined resource type so that you can ensure that whenever you create nagios resources you will get the right permissions.
Does this address your request, or have I not fully understood what you are looking for?
#2 Updated by Garth Kidd 8 months ago
- 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.