Jira (PUP-8346) File type content attribute accepts non-strings

[JIRA]

Title: Message Title

Pär Lindfors created an issue   Puppet / PUP-8346 File type content attribute accepts non-strings Issue Type: Bug Affects Versions: PUP 5.3.3 Assignee: Unassigned Components: Types and Providers Created: 2018/01/11 1:12 PM Priority: Normal Reporter: Pär Lindfors Puppet Version: 5.3.3, 3.8.7, 2.7.26 The documentation of the file type's content attribute is: "The desired contents of a file, as a string." However an array of strings is also accepted. When content is set to an array, the last element of the array is used as content. I don't know if this behaviour is intended, it is not documented as far as I can tell. This behaviour is not new, I tested using Puppet 5.3, 3.8, 2.7 and got the same result with all of them. Desired Behavior: I would expect the following to result in an evaluation error due to content not being a String value: file { '/tmp/foo': content => ["a\n", "b\n", "c\n"], } Actual Behavior: File '/tmp/foo' is created with the content "c\n". Add Comment   This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.