On Thursday, January 17, 2013 12:56:30 PM UTC-6, Josh Cooper wrote: > > Hi John, > > On Thu, Jan 17, 2013 at 6:56 AM, jcbollinger > <john.bo...@stjude.org<javascript:>> > wrote: > [...]
> > What I would expect on both Unix and Windows is that if the target file > > already exists and the resource declaration does not specify a mode, > then > > the current mode will not be changed. It is not a managed property. > > Good point. I would expect the behavior you describe, but that's not > what I'm seeing. > [...] Did puppet used to behave differently > in earlier versions [than 0.25.4]? > > I was able to verify that the same behavior is exhibited by Puppet 0.24.8. That behavior goes against basic Puppet principles, however: unmanaged resources and resource properties should not be modified by Puppet. It looks like that's the consensus opinion of those commenting on issue 5240, too. Basically, then, this is a longstanding, cross-platform bug. I have added a comment about this to issue 5240, as it probably makes sense to expand that issue to cover this matter, too. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/VtCl9YmeIS0J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
