Jira (PUP-1038) puppet fails if template contains invalid utf-8

[Mariusz Gronczewski (JIRA)]

Title: Message Title

Mariusz Gronczewski commented on an issue   Re: puppet fails if template contains invalid utf-8 Use cases: puppet manifests/modules in UTF-8 but some part of system is not using it - like legacy application still using some 8 bit coding like ISO-8859-2 or KOI8-R; and same config is used for say DB configuration and site name, in non-UTF encoding some badly designed configuration formats that use something like value=some-binary-string, example: linux "top" utility we used it for distributing sensitive data, as trying to secure filebucket paths so machine from project A couldn't download keys from project B was too much effort for the amount of different machines and projects we had, so we just put them into templates (as some apps for some insane reason insist on keeping parts of their configs as binary blobs) Of course, that is mostly solved by putting them into hiera, but sometimes "templates" are there just to add "this file is managed from puppet and you can find it $here" header, even if binary (or just non-utf) blob is passed from hiera. Add Comment   Puppet / PUP-1038 puppet fails if template contains invalid utf-8 If you attempt to use a file resource with a 'content' parameter pointing at a template, and the template contains binary content, you may get an error like this: {code}     Error: Failed to apply catalog: Parameter content failed: Munging failed for value ...     invalid byte sequence in UTF-8 {code} I've reproduced the failure in 2.7.16 and 3.x... 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/groups/opt_out.