Puppet

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?

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.

Just noticed that this is a duplicate of #3299. Closing this one in favor of the older issue.