Wrong permission on module files

[smoeding]

The problem from issue #164 is still not fixed in release 2.2.0. With r10k the module is not usable as some files have restricted file permissions. This module is the only module with this behaviour.

I expect the module build process to be the root cause here. If you look into the tar file that can be downloaded from forge.puppet.com you can actually see the missing read permission for others (mode 640) for some of the files (e.g. metadata.json).

[mcgege]

Hmm ... as I'm working with umask of 0027, the file and directory rights for other are missing in my local repo. For the git repo, that's no problem - if you checkout the repo for yourself, the permissions will be set according to your own umask.

But for the tar file the permissions get stored as they are in my local repo (when I execute pdk build), and that seems to be a problem for r10k ...

I have now changed my Release Workflow to fix the file rights before creating the tar file. Please try out the new release ...

(will address this issue in the pdk project)

[smoeding]

Looks good. The r10k deployment works now and doen't create files with restricted permissions any more.
Thanks!