forked from puppetlabs/puppetlabs-apt
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
do not specify file modes unless relevant
MODULES-10583 makes a good point: "why are you messing with my file permissions"? In my case, the entire reason I made the following change (in PR puppetlabs#906): ab2e06b MODULES-10548: make files readonly ... is exactly *because* Puppet was changing the file modes from under me. I was migrating from our own in-house APT module to the forge one, and our module did *not* intervene in those file modes: it left the file resources alone. Which means we could have a directive like this: File { owner => root, group => root, mode => '444', ensure => file, } ... which made all files readonly by default. So when I migrated to the Puppetlabs APT module, modes were changed to be writable, which I did not want. As I reasoned in MODULES-10548, having files readonly provides an excellent indicator that a file is managed by Puppet, even if some module does not add a warning header - either because it forgot or because it's impossible. But I also understand if people do not like that policy. I think the proper way of doing this is not specifying a mode at all, and let local site-specific policies apply. I specifically proppose this as an alternative to puppetlabs#921 because I believe adding more parameters to the resources will needlessly complicate the script, when we have a native, Puppet-DSL supported way of changing those modes according to the right scope and context. In a similar way, we might want to reconsider user and group ownership of the files, but that can be done in a later time. This reverts commit 316fd8f. Signed-off-by: Antoine Beaupré <anarcat@debian.org>
- Loading branch information
Showing
5 changed files
with
2 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters