Closed rnelson0 closed 9 years ago
And how could I forget the umask
[root@puppet ~]# umask
0022
I am having the same problem but with 777. Workaround is to set r10k::webhook::config::command_prefix: 'umask 0022;'
I know this is an issue not sure the best way to fix atm
I upgraded to 2.8.2 and now my environments are built with the right perms. I also noticed changes to the logging format which is awesome. Thanks so much!
On Wednesday, July 29, 2015, Zack Smith notifications@github.com wrote:
Closed #191 https://github.com/acidprime/r10k/issues/191 via 41d6cfd https://github.com/acidprime/r10k/commit/41d6cfdd63d7c9fe833b55f688fb3fabc021b4bb .
— Reply to this email directly or view it on GitHub https://github.com/acidprime/r10k/issues/191#event-368917627.
Rob Nelson rnelson0@gmail.com
The permissions I get for an environment I deploy my hand with r10k are 0644 (0755 for dirs); when the webhook deploys they are 0666 (0777 for dirs). The hook is not respecting root's umask and there appears to be no way to set the umask.
Here is my r10k configuration and parameters via yaml:
If there is some option I am missing, let me know and I can retest.