Jira (PUP-2156) file provider silent behaviour change for "mode"

[Per Cederqvist (JIRA)]

Title: Message Title

Per Cederqvist created an issue   Puppet / PUP-2156 file provider silent behaviour change for "mode" Issue Type: Bug Affects Versions: 3.5.0 Assignee: Kylo Ginsberg Components: Types and Providers Created: 04/Apr/14 5:51 AM Priority: Major Reporter: Per Cederqvist The type reference for file in Puppet 0.25.5 said: file { '/some/dir': mode => 644, recurse => true, } Ref: http://docs.puppetlabs.com/references/0.25.5/type.html#file I believe that there are many Puppet manifests out there that still writes file mode as 3-digit numbers and expect them to be interpreted as octal. Starting with Puppet 3.5.0, this would set the mode to 1204 instead of the intended 0644. The mode 755 becomes 1363 – which means that the file is world writable. I know that for a long time the documentation says that the mode should be specified as a four-digit octal value. But it doesn't say that it has to be a string. Specifying 4711 used to make a file setuid; starting in Puppet 3.5.0 is produces the nonsensical error message "The file mode specification is invalid: 4711". There has never been any deprecation warnings, so code written by the ancient documentation now suddenly behaves differently. Files that were supposed to be read-only can now become writable by everybody on the system. At the very least, this should have been mentioned in the release notes. Add Comment   This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.