I have noticed lately that on my development system (OS X) and my production Puppet master (CentOS 6.5) that when installing puppet modules using librarian-puppet the permissions of some modules and files is very restrictive to the point where the puppetmaster can't read the files. Some modules end up with all files being 0400, while some end up 0644 and some 0664. The files read-only to user are unable to be accessed by the Passenger based Puppet master and the files that sometimes go from 0664 to 0644 are creating a lot of noise in agent reports.
Is there a "defacto" standard for the appropriate permissions, especially for custom puppet providers/types/functions? I've noticed that whatever the permissions end up being on the master is what they get set to on the clients. I'm unsure if the permissions are being set by librarian-puppet, the puppet module command, or some other mechanism. The permissions are always like this after a "bundle exec librarian-puppet install". I've since had to put a script in my librarian-puppet repo that executes a find and modifies permissions, which does not seem right. Curious if anyone else has seen this or has suggestions for how to debug. Thanks - Trey -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/bc4f86d5-0c65-4ec6-bc98-43f437a611e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
