Jira (PUP-7395) Puppet::Util.replace_file ignores mode parameter when file exists

[Ethan Brown (JIRA)]

Title: Message Title

Ethan Brown created an issue   Puppet / PUP-7395 Puppet::Util.replace_file ignores mode parameter when file exists Issue Type: Improvement Assignee: Unassigned Created: 2017/03/23 2:20 PM Priority: Normal Reporter: Ethan Brown Documentation for replace_file very explicitly states: # As far as possible the state of the existing file, such as mode, is # preserved. This works hard to avoid loss of any metadata, but will result # in an inode change for the file. It seems a bit peculiar to pass a mode value into the API and have it ignored - so I think the order of precedent here seems incorrect. It's also possible I've misunderstood all the use cases here or any behavior Puppet might typically inherit while running as root (which could work around the issue). Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.